Re: Why pg_dump overwrites dump file? - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Why pg_dump overwrites dump file?
Date
Msg-id 46AFE2A5-8189-4868-9CF0-E2E58E9DFCC5@yesql.se
Whole thread Raw
In response to Why pg_dump overwrites dump file?  (Chao Li <li.evan.chao@gmail.com>)
List pgsql-hackers
> On 14 Oct 2025, at 07:42, Chao Li <li.evan.chao@gmail.com> wrote:

> Behaviors of the two types of pg_dump are inconsistent, I wonder if that’s by design?

It does admittedly seem odd that --file works differently for files and
directories, but at this point it might be behavior that users expect and
changing it might break current usecases?  Not sure what the best option is
here.

Another inconsistency is that the documentation states this:

    "In this case the directory is created by pg_dump and must not exist
    before."

..which isn't true, since it will happily reuse an existing directory as long as
it's empty, the comment in the code makes the intention clear:

  /*
   * create_or_open_dir
   *
   * This will create a new directory with the given dirname. If there is
   * already an empty directory with that name, then use it.
   */

So regardless it seems we should something like the attached at least.

--
Daniel Gustafsson


Attachment

pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Changing shared_buffers without restart
Next
From: torikoshia
Date:
Subject: Re: Enhancing Memory Context Statistics Reporting