| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade vs extension upgrades |
| Date: | 2017-04-13 15:48:47 |
| Message-ID: | abef5a4b-be3b-adaa-d769-27355670cedc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-13 16:00:12 | Re: pg_statistic_ext.staenabled might not be the best column name |
| Previous Message | Robert Haas | 2017-04-13 15:38:08 | Re: pg_dump emits ALTER TABLE ONLY partitioned_table |