From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <davecramer(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_upgrade does not upgrade pg_stat_statements properly |
Date: | 2021-07-29 23:26:46 |
Message-ID: | 202107292326.s4weqxvr3wmb@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021-Jul-29, Bruce Momjian wrote:
> On Thu, Jul 29, 2021 at 06:29:11PM -0400, Tom Lane wrote:
> > No, because dump/restore does not have this issue. Regular pg_dump just
> > issues "CREATE EXTENSION" commands, so you automatically get the target
> > server's default version.
>
> Oh, so pg_upgrade does it differently so the oids are preserved?
Have a look at pg_dump --binary-upgrade output :-)
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
"Ellos andaban todos desnudos como su madre los parió, y también las mujeres,
aunque no vi más que una, harto moza, y todos los que yo vi eran todos
mancebos, que ninguno vi de edad de más de XXX años" (Cristóbal Colón)
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2021-07-29 23:27:32 | Re: Use WaitLatch for {pre, post}_auth_delay instead of pg_usleep |
Previous Message | Dave Cramer | 2021-07-29 23:06:25 | Re: pg_upgrade does not upgrade pg_stat_statements properly |