Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #18245: pg_restore accepts same output file name as input file name - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: BUG #18245: pg_restore accepts same output file name as input file name
Date
Msg-id E7AEB7F8-BB3E-403F-ACDB-E06AF4E37861@yesql.se
Whole thread Raw
In response to BUG #18245: pg_restore accepts same output file name as input file name  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18245: pg_restore accepts same output file name as input file name
List pgsql-bugs
Tree view 
> On 13 Dec 2023, at 04:39, PG Bug reporting form <noreply@postgresql.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

pgsql-bugs by date:

Previous
From: Aksel Allas
Date:
Subject: Re: BUG #18242: pg_dump with non-superuser from pg14 to pg15 fails on ALTER FUNCTION
Next
From: PG Bug reporting form
Date:
Subject: BUG #18246: pgstathashindex() attempts to read invalid file for hash index attached to partitioned table