From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Kartyshov Ivan <i(dot)kartyshov(at)postgrespro(dot)ru> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: get oldest LSN - function |
Date: | 2016-02-28 08:36:57 |
Message-ID: | CAB7nPqSJh5=idbhAnS3tf09O5zK_RcK2cTfr6Rti532c-ykEdg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Feb 28, 2016 at 4:40 PM, Kartyshov Ivan wrote:
> It will not satisfy our purposes and our administrators for three reasons.
> 1) DBA set me task to get the oldest number that present in WAL, not last
Yeah I got that.
> 2) Surely we can choose the oldest segment from list "pg_ls_dir('pg_xlog')"
> of segments and calculate the first LSN by hand, but it is not what we want
> to do manually.
That's where I am not following. In any case you are just one SQL
query away from the result. And actually your patch is incorrect I
think. If you care about the oldest record available you should look
for the first LSN position of the oldest segment, no? What you are
calculating now is the oldest virtual LSN position in local pg_xlog.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Yury Zhuravlev | 2016-02-28 08:51:03 | Re: [PATH] Correct negative/zero year in to_date/to_timestamp |
Previous Message | Kartyshov Ivan | 2016-02-28 07:40:05 | Re: proposal: get oldest LSN - function |