Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats

From: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats
Date: 2026-02-19 06:05:24
Message-ID: CAC6VRoYQLKJfUYgA6qznz+hu08Q34j9F_6UQ7ZAPu-q2KWbUsg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 18, 2026 at 8:43 PM Nathan Bossart <nathandbossart(at)gmail(dot)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,

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-02-19 06:16:03 Re: pgstat include expansion
Previous Message Peter Smith 2026-02-19 05:55:29 DOCS - pg_walsummary filename