| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Two noncritical bugs of pg_waldump |
| Date: | 2022-01-27 20:18:16 |
| Message-ID: | 20220127201816.GA554411@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 27, 2022 at 01:23:06PM +0900, Kyotaro Horiguchi wrote:
> So the issue there is neither EndRecPtr and ReadRecPtr always points
> to the current read LSN. The first proposal from Nathen was to use
> currRecPtr but it was a private member. But after discussion, it
> seems to me it is (at least now) exactly what we need here so if we
> ofccially exposed the member the problem would be blown away. Do you
> want to conitnue that?
Presumably there is a good reason for keeping it private, but if not, maybe
that is a reasonable approach to consider. I don't think we wanted to
proceed with the approaches discussed on the old thread, anyway.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-01-27 20:18:51 | Re: Design of pg_stat_subscription_workers vs pgstats |
| Previous Message | Robert Haas | 2022-01-27 19:43:57 | Re: pgsql: Server-side gzip compression. |