Re: pg_upgrade fails with an error "object doesn't exist"

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Vaibhav Dalvi <vaibhav(dot)dalvi(at)enterprisedb(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade fails with an error "object doesn't exist"
Date: 2025-06-17 06:28:34
Message-ID: 1E572409-796A-4566-9DD7-662F02AA16C6@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 17 Jun 2025, at 04:58, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> There are enough moving parts in that area
> already that I'm not eager to add more constraints to what pg_dump
> needs to do.

Agreed. I we were to do anything I think a check in pg_upgrade would be more
appropriate than altering pg_dump (but I'm not sure it's worth spending the
cycles in every upgrade to test for this, the check phase is already quite
extensive).

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-06-17 06:30:58 Re: Replication slot is not able to sync up
Previous Message Peter Eisentraut 2025-06-17 05:46:28 Re: Mention the default io_method?