| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Show redo LSN in checkpoint logs |
| Date: | 2021-09-09 05:58:35 |
| Message-ID: | 20210909.145835.717315905993410072.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello.
Sometimes, I needed to infer where a past checkpoint make wal segments
unnecessary up to, or just to know the LSN at a past point in
time. But there's no convenient source for that.
The attached small patch enables me (or us) to do that by looking into
server log files.
> LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.008 s, sync=0.035 s, total=0.064 s; sync files=4, longest=0.017 s, average=0.009 s; distance=16420 kB, estimate=16420 kB, redo=0/30091D8
Does that make sense?
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| show_redo_lsn_in_checkpoint_logs.patch | text/x-patch | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2021-09-09 06:13:02 | Re: row filtering for logical replication |
| Previous Message | Pavel Stehule | 2021-09-09 05:37:06 | Re: [PROPOSAL] new diagnostic items for the dynamic sql |