Re: list tablespaces named in custom format dump

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: list tablespaces named in custom format dump
Date: 2022-05-23 17:19:21
Message-ID: 66d925ce-5a4e-e3e0-583a-f1c2574948dc@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/23/22 11:07, Adrian Klaver wrote:
> On 5/23/22 10:01 AM, Rob Sargent wrote:
>> On 5/23/22 11:00, Adrian Klaver wrote:
>>> On 5/23/22 9:54 AM, Rob Sargent wrote:
>>>> On 5/23/22 10:50, Adrian Klaver wrote:
>>>
>>>> Roger that, but does the dump of a database name the tablespaces
>>>> from which the objects were retrieved? And if so, is that accessible?
>>>>
>>>
>>>
>>> https://www.postgresql.org/docs/14/app-pgrestore.html
>>>
>>> "--no-tablespaces
>>>
>>>     Do not output commands to select tablespaces. With this option,
>>> all objects will be created in whichever tablespace is the default
>>> during restore.
>>> "
>>>
>>> Would indicate it does. I don't have cluster set up with tablespaces
>>> to test, but I would try:
>>>
>>> pg_restore -l <custom_format_file>
>>>
>>> This will produce a Table of Contents for the file.
>>>
>> Ah, missed that. Thanks.
>> (Now I'll have to find the version used to dump the db...)
>
> If you have it just use the Postgres 14 version of pg_restore it will
> be able to read older files from older versions of pg_dump.
>
>
This is great news.  I do have pg14.  I thought you had to dump with the
save version as restore.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message dzagashev@gmail.com 2022-05-23 17:28:15 psql connect over ssl load balancer
Previous Message Durumdara 2022-05-23 17:14:25 Re: PLPGSQL - extra column existence in trigger