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-18 15:13:19
Message-ID: aZXXD4HhJjACM-3j@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2026-02-18 15:15:09 some validate_relation_kind() tidying
Previous Message Alvaro Herrera 2026-02-18 15:10:38 Re: pgstat include expansion