| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, boekewurm+postgres(at)gmail(dot)com, melanieplageman(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org, pg(at)bowt(dot)ie |
| Subject: | Re: Add pg_walinspect function with block info columns |
| Date: | 2023-03-10 01:20:05 |
| Message-ID: | CALj2ACVJGqJpoxpXQnKv_5sN7wSV5OPWYA5Lq7KkcOvE=utxBw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 10, 2023 at 6:43 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> I'd really like to do something about the errors we raise in the
> module when specifying LSNs in the future for this release, now. I
> got annoyed by it again this morning while doing \watch queries that
> kept failing randomly while stressing this patch.
Perhaps what is proposed here
https://www.postgresql.org/message-id/CALj2ACWqJ+m0HoQj9qkAV2uQfq97yk5jN2MOdfKcXusXsyptKQ@mail.gmail.com
might help and avoid many errors around input LSN validations. Let's
discuss that in that thread.
--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-03-10 01:21:55 | Re: Sub-millisecond [autovacuum_]vacuum_cost_delay broken |
| Previous Message | Thomas Munro | 2023-03-10 01:13:14 | Re: Sub-millisecond [autovacuum_]vacuum_cost_delay broken |