pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ryan Murphy <ryanfmurphy@gmail.com>
To: pgsql-hackers@postgresql.org
Cc: Kyotaro Horiguchi <horiguchi.kyotaro@lab.ntt.co.jp>
Subject: Re: Bug in Physical Replication Slots (at least 9.5)?
Date: Thu, 06 Jul 2017 15:00:36 +0000
Message-ID: <20170706150036.1381.32532.pgcf@coridan.postgresql.org> (raw)
In-Reply-To: <CAB7nPqT8dQk_Ce29YQ0CKAQ7htLDyUHNdFv6dELe4PkYr3SSjA@mail.gmail.com>
References: <CACJqAM3xVz0JY1XFDKPP+JoJAjoGx=GNuOAshEDWCext7BFvCQ@mail.gmail.com>
	<CAB7nPqT8dQk_Ce29YQ0CKAQ7htLDyUHNdFv6dELe4PkYr3SSjA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Poking this.  Looking back through the discussion, this issue has been reproduced by multiple people.  The patch still applies to HEAD without issues.  I have no experience with PostgreSQL replication, so I'm not qualified to really review this.  From what I can see with the patch, it's just a small block of code added to /src/backend/replication/walreceiver.c to handle some edge case where the WAL file no longer exists or something.

I think one thing that would help move this forward is if we edited the patch to include a comment explaining why this new code is necessary.  There's lots of great discussion on this issue in the email list, so if a summary of that gets into the code I think it would make the patch easier to understand and make the new walreceiver.c less confusing.
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


view thread (58+ messages)  latest in thread

Message-ID: <20170706150036.1381.32532.pgcf@coridan.postgresql.org>
Permalink:  ../20170706150036.1381.32532.pgcf@coridan.postgresql.org/
Also on:    postgresql.org/message-id/20170706150036.1381.32532.pgcf@coridan.postgresql.org

 · 

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: ryanfmurphy@gmail.com, horiguchi.kyotaro@lab.ntt.co.jp
  Subject: Re: Bug in Physical Replication Slots (at least 9.5)?
  In-Reply-To: <20170706150036.1381.32532.pgcf@coridan.postgresql.org>

* 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