From: | Perumal Raj <perucinci(at)gmail(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(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 22:21:11 |
Message-ID: | CALvqh4o-8-3NOrYkPA_RweSfMMT21pJ-70U0Qz6WgDB7ng4dLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Hi Justin
Does it mean that these functions are default and came with 9.2 ?
I am wondering how these functions are created in the DB as the
library($libdir/pg_reorg) is not exists in system
Note:
My schema name is reorg not pg_reorg
On Mon, Mar 4, 2019 at 1:45 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> 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 | Justin Pryzby | 2019-03-04 22:32:21 | Re: Question about pg_upgrade from 9.2 to X.X |
Previous Message | Julie Nishimura | 2019-03-04 21:59:13 | master-> 2 hot standbys |
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2019-03-04 22:32:21 | Re: Question about pg_upgrade from 9.2 to X.X |
Previous Message | Bossart, Nathan | 2019-03-04 22:20:39 | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |