Re: [HACKERS] Draft release notes for next week's back-branchreleases - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [HACKERS] Draft release notes for next week's back-branchreleases
Date
Msg-id ce79106a-472b-5374-97ca-43eaf72d00a8@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Draft release notes for next week's back-branch releases  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 06/05/17 19:38, Tom Lane wrote:
> Petr Jelinek <petr.jelinek@2ndquadrant.com> writes:
>> On 06/05/17 19:15, Tom Lane wrote:
>>> (Or, wait a minute.  That documentation only applies to v10, but we
>>> need to be writing this relnote for 9.6 users.  What terminology should
>>> we be using anyway?)
> 
>> Yeah we need to somehow mention that it only affects 3rd party tools
>> using logical decoding.
> 
>> "The initial snapshot created for a logical decoding slot was
>> potentially incorrect.  This could allow the 3rd party tools using
>> the logical decoding to copy incomplete existing(?) data.  This was
>> more likely to happen if the source server was busy at the time of
>> slot creation, or if two slots were created concurrently."
> 
>>> Also, do we need to recommend that people not trust any logical replicas
>>> at this point, but recreate them after installing the update?
> 
>> Yes, but only if there was preexisting data *and* there was concurrent
>> activity on the server when the "replication" was setup.
> 
> OK, I can work with this.  Thanks for the help!
> 

Great, thanks.

--  Petr Jelinek                  http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: [HACKERS] Get stuck when dropping a subscription during synchronizing table
Next
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] Other formats in pset like markdown, rst, mediawiki