| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
| Cc: | Jan Wieck <jan(at)wi3ck(dot)info>, 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 11:40:52 |
| Message-ID: | 20210730114052.smbpww3l5yw6pypi@nol |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2021-07-30 11:47:18 | Re: A qsort template |
| Previous Message | Dave Cramer | 2021-07-30 11:33:55 | Re: pg_upgrade does not upgrade pg_stat_statements properly |