Re: pg_upgrade does not upgrade pg_stat_statements properly

From: Jan Wieck <jan(at)wi3ck(dot)info>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Dave Cramer <davecramer(at)postgres(dot)rocks>
Cc: Bruce Momjian <bruce(at)momjian(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-30 16:44:17
Message-ID: 4fbc3375-db33-694b-1635-0a6796da6023@wi3ck.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/30/21 7:40 AM, Julien Rouhaud wrote:
> On Fri, Jul 30, 2021 at 07:33:55AM -0400, Dave Cramer wrote:
>>
>> Ah, ok, got it, thanks. Well I'm not sure how to deal with this.
>> The only thing I can think of is that we add a post_upgrade function to the
>> API.
>>
>> All extensions would have to implement this.
>
> It seems like a really big hammer for a niche usage. As far as I know I'm the
> only one who wrote an extension that can create different objects depending on
> the server version, so I'm entirely fine with dealing with that problem in my
> extension rather than forcing everyone to implement an otherwise useless API.
>
> Now if that API can be useful for other cases or if there are other extensions
> with similar problems that would be different story.
>

I haven't worked on it for a while, but I think pl_profiler does the
same thing, so you are not alone.

Jan

--
Jan Wieck

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-07-30 16:49:34 Re: Have I found an interval arithmetic bug?
Previous Message Jan Wieck 2021-07-30 16:43:04 Re: pg_upgrade does not upgrade pg_stat_statements properly