On 9/19/18 4:53 AM, Michael Paquier wrote:
> On Tue, Sep 18, 2018 at 12:32:54PM +0200, Adrien NAYRAT wrote:
>> A few days ago I was surprised a CREATE TABLE containing FK constraint was
>> stuck due to an automatic vacuum freeze (which took ShareUpdateExclusiveLock
>> if I remember) on referenced t
> On Sep 19, 2018, at 9:43 AM, Tom Lane wrote:
>
> =?utf-8?q?PG_Doc_comments_form?= writes:
>> This sentence should not use a semicolon: "Both the ADD TABLE and DROP TABLE
>> operations are transactional; so the table will start or stop replicating at
>> the correct snapshot once the transacti
=?utf-8?q?PG_Doc_comments_form?= writes:
> This sentence should not use a semicolon: "Both the ADD TABLE and DROP TABLE
> operations are transactional; so the table will start or stop replicating at
> the correct snapshot once the transaction has committed."
That looks perfectly fine to me. More
The following documentation comment has been logged on the website:
Page:
https://www.postgresql.org/docs/10/static/logical-replication-publication.html
Description:
This sentence should not use a semicolon: "Both the ADD TABLE and DROP TABLE
operations are transactional; so the table will start
