| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Andrey Salnikov <andrey(dot)salnikov(at)dataegret(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16125: Crash of PostgreSQL's wal sender during logical replication |
| Date: | 2019-11-27 15:35:06 |
| Message-ID: | 20191127153506.tuqlckfj426rkrlb@development |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 27, 2019 at 11:57:00AM -0300, Alvaro Herrera wrote:
>On 2019-Nov-27, Alvaro Herrera wrote:
>
>> I think pg_waldump should print out the speculativeness of an insertion.
>
>Ah, in pg12 we do print the "flags" for the insertion. But earlier
>releases don't. IMO we should have backpatched that change, as I said
>in https://postgr.es/m/20180423160216.m2yjhx67grofg7h5@alvherre.pgsql
>but I was outvoted.
>
Hmmmm, yeah. I still think the decision not to backpatch was reasonable,
although it seems it might have been useful in this particular case.
But hey, it should not be that difficult to build a custom pg_waldump
version with that patch applied, and decode the WAL segment. It can even
be done on a completely separate system, it's just a single binary.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-11-27 17:59:35 | Re: BUG #16125: Crash of PostgreSQL's wal sender during logical replication |
| Previous Message | Alvaro Herrera | 2019-11-27 14:57:00 | Re: BUG #16125: Crash of PostgreSQL's wal sender during logical replication |