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

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: tushar <tushar(dot)ahuja(at)enterprisedb(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-20 18:37:45
Message-ID: aZip-S5Be7hZv1gd@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 19, 2026 at 11:35:24AM +0530, tushar wrote:
> 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.

I'm not sure. While I agree that it's a little weird, AFAICT it's behaved
this way for a long time, so changing it risks breaking existing scripts.
I suspect that trade-off is not worth it in this case.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-02-20 19:17:42 Re: ecdh support causes unnecessary roundtrips
Previous Message Andrey Borodin 2026-02-20 18:36:06 Re: Fix XLogFileReadAnyTLI silently applying divergent WAL from wrong timeline