Re: BUG #14719: Logical replication unexpected behaviour when target table has missing columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: garton(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14719: Logical replication unexpected behaviour when target table has missing columns
Date: 2017-06-27 15:33:55
Message-ID: 29708.1498577635@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

garton(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message lizenko79 2017-06-27 16:37:57 BUG #14720: getsockopt(TCP_KEEPALIVE) failed: Option not supported by protocol
Previous Message David G. Johnston 2017-06-27 15:32:44 Re: BUG #14719: Logical replication unexpected behaviour when target table has missing columns