pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Antonin Houska <ah@cybertec.at>
Cc: Arseny Sher <a.sher@postgrespro.ru>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Fix slot's xmin advancement and subxact's lost snapshots in decoding.
Date: Mon, 18 Jun 2018 14:04:19 -0400
Message-ID: <20180618180419.mysc6nxvntgvfgg2@alvherre.pgsql> (raw)
In-Reply-To: <15387.1528700867@localhost>

On 2018-Jun-11, Antonin Houska wrote:

> Arseny Sher <a.sher@postgrespro.ru> wrote:
> > Please see detailed description of the issues, tests which reproduce
> > them and fixes in the attached patch.
> 
> I've played with your tests and gdb for a while, both w/o and with your
> patch. I think I can understand both problems. I could not invent simpler way
> to fix them.
> 
> One comment about the coding: since you introduce a new transaction list and
> it's sorted by LSN, I think you should make the function AssertTXNLsnOrder()
> more generic and use it to check the by_base_snapshot_lsn list too. For
> example call it after the list insertion and deletion in
> ReorderBufferPassBaseSnapshot().

I've been going over this patch also, and I've made a few minor edits of
the patch and the existing code as I come to understand what it's all
about.

> Also I think it makes no harm if you split the diff into two, although both
> fixes use the by_base_snapshot_lsn field.

Please don't.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (13+ messages)  latest in thread

Message-ID: <20180618180419.mysc6nxvntgvfgg2@alvherre.pgsql>
Permalink:  ../20180618180419.mysc6nxvntgvfgg2@alvherre.pgsql/
Also on:    postgresql.org/message-id/20180618180419.mysc6nxvntgvfgg2@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@2ndquadrant.com, ah@cybertec.at, a.sher@postgrespro.ru
  Subject: Re: Fix slot's xmin advancement and subxact's lost snapshots in decoding.
  In-Reply-To: <20180618180419.mysc6nxvntgvfgg2@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox