Re: Question about pg_dump + pg_restore + pg_toast

From: Edwin UY <edwin(dot)uy(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Question about pg_dump + pg_restore + pg_toast
Date: 2025-03-01 20:53:48
Message-ID: CA+wokJ8H8AcGv5c7xVj1PV8UYkB08KLxqF8bvLho6HqfX7mN1A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

If need be, do I manually edit the dumpfile using something like vi?

On Tue, Feb 25, 2025 at 12:06 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
wrote:

> Run the PG12 pg_dump just before the pg_upgrade.
>
> Forward compatibility in maintenance utilities is (usually) guaranteed.
> Backwards compatibility (which is what you want)? Not so much.
>
> On Mon, Feb 24, 2025 at 4:31 PM Edwin UY <edwin(dot)uy(at)gmail(dot)com> wrote:
>
>> Yikes, I thought it is alright so long as I use the latest version of
>> pg_dump and restore.
>> Thanks for the warning.
>>
>> On Tue, Feb 25, 2025 at 12:35 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
>> wrote:
>>
>>> On Mon, 2025-02-24 at 22:19 +1300, Edwin UY wrote:
>>> > We are upgrading this database from v12 to v16 and we want to do a
>>> dump of it in case we decided to do a restore from v16 to v12.
>>> > SO, after the upgrade, in case we want to rollback to v12, we will do
>>> a pg_dump using v16 and then using v12 pg_restore
>>>
>>> Be warned that downgrade is not supported and restoring the dump to v12
>>> might well fail.
>>> You might have to manually edit the dump file until you can restore it
>>> without errors.
>>>
>>> Yours,
>>> Laurenz Albe
>>>
>>> --
>>>
>>> *E-Mail Disclaimer*
>>> Der Inhalt dieser E-Mail ist ausschliesslich fuer den
>>> bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene
>>> Adressat
>>> dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte,
>>> dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung
>>> oder
>>> Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie,
>>> sich
>>> in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
>>>
>>> *CONFIDENTIALITY NOTICE & DISCLAIMER
>>> *This message and any attachment are
>>> confidential and may be privileged or otherwise protected from
>>> disclosure
>>> and solely for the use of the person(s) or entity to whom it is
>>> intended.
>>> If you have received this message in error and are not the intended
>>> recipient, please notify the sender immediately and delete this message
>>> and
>>> any attachment from your system. If you are not the intended recipient,
>>> be
>>> advised that any use of this message is prohibited and may be unlawful,
>>> and
>>> you must not copy this message or attachment or disclose the contents to
>>> any other person.
>>>
>>
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2025-03-01 21:27:19 Re: Question about pg_dump + pg_restore + pg_toast
Previous Message shammat 2025-03-01 19:20:59 Re: fast way to run a query with 7 thousand constant values