Re: [BUGS] BUG #14719: Logical replication unexpected behaviour when target table has missing columns - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] BUG #14719: Logical replication unexpected behaviour when target table has missing columns
Date
Msg-id 29708.1498577635@sss.pgh.pa.us
Whole thread Raw
In response to [BUGS] BUG #14719: Logical replication unexpected behaviour when targettable has missing columns  (garton@gmail.com)
Responses Re: [BUGS] BUG #14719: Logical replication unexpected behaviour whentarget table has missing columns  (Martin Garton <garton@gmail.com>)
List pgsql-bugs
garton@gmail.com writes:
> The documentation states:

> "The target table can have additional columns not provided by the published
> table. Those will be filled with their default values."

> However, when I added a column on the source database, the target began to
> error:

> ERROR:  logical replication target relation "public.foo" is missing some
> replicated columns

> This seems to contradict the documentation.

Um, by my reading, what that paragraph is describing is the opposite case.
It says you can add extra columns to the target table, not the source one.
        regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [BUGS] BUG #14719: Logical replication unexpected behaviour whentarget table has missing columns
Next
From: lizenko79@gmail.com
Date:
Subject: [BUGS] BUG #14720: getsockopt(TCP_KEEPALIVE) failed: Option not supported byprotocol