From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
---|---|
To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
Subject: | Re: Combine pg_walinspect till_end_of_wal functions with others |
Date: | 2023-03-06 15:21:47 |
Message-ID: | CAEze2WjiG4QKoXJi5aN-F8C4T7jz=--+jB4OJz48+GjdP0+f7A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 6 Mar 2023 at 16:06, Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> If we try to make these functions figure out the oldest WAl file and
> start from there, then it'll unnecessarily complicate the APIs and
> functions. If we still think we need a better function for the users
> to figure out the oldest WAL file, perhaps, add a SQL-only
> view/function to pg_walinspect that returns "select name from
> pg_ls_waldir() order by name limit 1;", but honestly, that's so
> trivial.
That "order by name limit 1" has subtle bugs when you're working on a
system that has experienced timeline switches. It is entirely possible
that the first file (as sorted by the default collation) is not the
first record you can inspect, or even in your timeline's history.
Kind regards,
Matthias van de Meent
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2023-03-06 15:30:22 | Re: meson: Optionally disable installation of test modules |
Previous Message | Tom Lane | 2023-03-06 15:12:06 | Re: wrong results due to qual pushdown |