From: | Dave Cramer <davecramer(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 15:01:43 |
Message-ID: | CADK3HHJXMMtGBhAgDw7NhqUmzSN78Wu5Us9VoXzS2y8mZH0Lyw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> OK, I went with this new text. There is confusion over install vs copy,
> and whether this is happening at the operating system level or the SQL
> level. I tried to clarify that, but I am not sure I was successful. I
> also used the word "extension" since this is more common than "custom".
>
Much better, however I'm unclear on whether CREATE EXTENSION is actually
executed on the upgraded server.
From what I could gather it is not, otherwise the new function definitions
should have been in place.
I think what happens is that the function definitions are copied as part of
the schema and pg_extension is also copied.
Dave
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-07-29 15:06:41 | Re: [postgres_fdw] add local pid to fallback_application_name |
Previous Message | Daniil Zakhlystov | 2021-07-29 14:57:09 | Re: libpq compression |