Re: [HACKERS] pg_upgrade vs extension upgrades - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] pg_upgrade vs extension upgrades
Date
Msg-id abef5a4b-be3b-adaa-d769-27355670cedc@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] pg_upgrade vs extension upgrades  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [HACKERS] pg_upgrade vs extension upgrades  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 4/12/17 22:56, Bruce Momjian wrote:
> Is pg_upgrade the right place for an extension upgrade script?  When
> pg_upgrade started creating an incremental-analyze script, people
> thought it should be more generic so it was moved to vacuumdb
> --analyze-in-stages.  Seems we should do the same thing for the
> extension upgrade script.

Yeah, many of the things that pg_upgrade would do or suggest after an
upgrade could also apply to other upgrade methods, such as by logical
replication.  So offering them separately would be good.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] pg_dump emits ALTER TABLE ONLY partitioned_table
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] pg_statistic_ext.staenabled might not be the bestcolumn name