From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Combine pg_walinspect till_end_of_wal functions with others |
Date: | 2023-03-07 04:36:17 |
Message-ID: | ZAa/Qczw/1Oi7DOH@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 07, 2023 at 09:13:46AM +0800, Julien Rouhaud wrote:
> It's problematic to install the extension if we rely on upgrade scripts only.
> We could also provide a pg_walinspect--1.2.sql file and it would just work, and
> that may have been a good idea if there wasn't also the problem of people still
> having the version 1.1 locally installed, as we don't want them to see random
> failures like "could not find function ... in file ...", or keeping the ability
> to install the former 1.1 version (with those functions bypassed).
Why would we need a 1.2? HEAD is the only branch with pg_walinspect
1.1, and it has not been released yet.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2023-03-07 04:42:20 | Re: Combine pg_walinspect till_end_of_wal functions with others |
Previous Message | Michael Paquier | 2023-03-07 04:32:22 | Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes? |