Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats - Mailing list pgsql-hackers

From tushar
Subject Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats
Date
Msg-id CAC6VRoYQLKJfUYgA6qznz+hu08Q34j9F_6UQ7ZAPu-q2KWbUsg@mail.gmail.com
Whole thread
In response to Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats
List pgsql-hackers


On Wed, Feb 18, 2026 at 8:43 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
On Wed, Feb 18, 2026 at 04:13:11PM +0530, tushar wrote:
> I observed that pg_restore attempts to set default_tablespace from a Tar
> archive even if --no-tablespaces was used during pg_dump.

Correct.  The documentation for pg_dump --no-tablespaces states the
following:

    This option is ignored when emitting an archive (non-text) output file.
    For the archive formats, you can specify the option when you call
    pg_restore.

Thanks for pointing that out. Since this appears to be the expected behavior, should we leave it as is rather than attempting to 'fix' or improve it? 
if --not-tablespace already specified at the time of pg_dump ( not sure why it is ignored; it should throw an error if not supported)  
then it makes sense that it wouldn't be necessary for pg_restore time, seems redundant.

regards,

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: DOCS - pg_walsummary filename
Next
From: Amit Kapila
Date:
Subject: Re: pgstat include expansion