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

From Nathan Bossart
Subject Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats
Date
Msg-id aZip-S5Be7hZv1gd@nathan
Whole thread Raw
In response to Re: Discrepancy in --no-tablespaces behavior between Tar and Plain-text formats  (tushar <tushar.ahuja@enterprisedb.com>)
List 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



pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: Fix XLogFileReadAnyTLI silently applying divergent WAL from wrong timeline
Next
From: Tom Lane
Date:
Subject: Re: ecdh support causes unnecessary roundtrips