| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Perumal Raj <perucinci(at)gmail(dot)com> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Question about pg_upgrade from 9.2 to X.X |
| Date: | 2019-03-04 21:45:01 |
| Message-ID: | 20190304214501.GP29584@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, Mar 04, 2019 at 01:37:30PM -0800, Perumal Raj wrote:
> I could see bunch of functions under reorg schema.
Those functions are the ones preventing you from upgrading.
You should drop schema pg_reorg cascade.
You can run it in a transaction first to see what it will drop.
But after the upgrade, you can CREATE EXTENSION pg_repack, which is a fork of
pg_reorg, which is itself no longer maintained.
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julie Nishimura | 2019-03-04 21:59:13 | master-> 2 hot standbys |
| Previous Message | Perumal Raj | 2019-03-04 21:37:30 | Re: Question about pg_upgrade from 9.2 to X.X |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-03-04 21:59:13 | Re: Making all nbtree entries unique by having heap TIDs participate in comparisons |
| Previous Message | Andres Freund | 2019-03-04 21:43:50 | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |