| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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 05:47:01 |
| Message-ID: | 20230307054701.ay3ukfm23ktihufj@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 07, 2023 at 01:56:24PM +0900, Michael Paquier wrote:
> On Tue, Mar 07, 2023 at 12:42:20PM +0800, Julien Rouhaud wrote:
> > ah right I should have checked. but the same ABI compatibility concern
> > still exists for version 1.0 of the extension.
>
> Yes, we'd better make sure that the past code is able to run, at
> least. Now I am not really convinced that we have the need to enforce
> an error with the new code even if 1.0 is still installed,
So keep this "deprecated" C function working, as it would only be a few lines
of code?
> so as it is
> possible to remove all the traces of the code that triggers errors if
> an end LSN is higher than the current insert LSN for primaries or
> replayed LSN for standbys.
+1 for that
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-03-07 06:14:51 | Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes? |
| Previous Message | Michael Paquier | 2023-03-07 05:44:49 | Re: Add pg_walinspect function with block info columns |