| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | garton(at)gmail(dot)com |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <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:32:44 |
| Message-ID: | CAKFQuwY4zqTR2ABCLGg8V6fDDonDQE0cEbitjPqLi4=chf-gvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jun 27, 2017 at 1:28 AM, <garton(at)gmail(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14719
> Logged by: Martin Garton
> Email address: garton(at)gmail(dot)com
> PostgreSQL version: 10beta1
> Operating system: Linux xxxxxx 4.9.0-3-amd64 #1 SMP Debian 4.9.30-
> Description:
>
> 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.
>
The target table can have extra columns - what you describe is a scenario
where it has fewer (i.e., you added a column to the source table).
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-06-27 15:33:55 | Re: BUG #14719: Logical replication unexpected behaviour when target table has missing columns |
| Previous Message | Tom Turelinckx | 2017-06-27 13:22:10 | Re: Bus error in formatting.c NUM_numpart_to_char (9.4.12, 9.6.3, sparc) |