| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | mb(dot)alzouabi(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18245: pg_restore accepts same output file name as input file name |
| Date: | 2023-12-13 08:44:26 |
| Message-ID: | E7AEB7F8-BB3E-403F-ACDB-E06AF4E37861@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 13 Dec 2023, at 04:39, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> Please let it fail when the user passes the same name for the output as the
> input.
I think this sounds like a fair restriction, input and output being the same
seems much more likely to be a copy/paste issue than an interesting usecase.
Something like the attached (untested) sketch should be enough I think.
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| pg_restore_filecheck.diff | application/octet-stream | 726 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-12-13 09:00:01 | BUG #18246: pgstathashindex() attempts to read invalid file for hash index attached to partitioned table |
| Previous Message | Aksel Allas | 2023-12-13 06:23:15 | Re: BUG #18242: pg_dump with non-superuser from pg14 to pg15 fails on ALTER FUNCTION |