| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical replication without a Primary Key |
| Date: | 2017-12-07 14:37:17 |
| Message-ID: | CAKFQuwZYqGRF-66e1tOWtmdk7qUi3PXnAsswF=T6-e1ZaB6r+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday, December 7, 2017, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 12/6/17 19:03, Joshua D. Drake wrote:
>
> >
> > How does that work? Is it using one of the hidden columns on a row?
>
> It means that for example if an update record is produced, the entire
> row is included in the record as the key.
>
>
IOW, IIUC, whether defined or not the user data portion of the table must,
as a whole, provide a natural unique key if you are going to use logical
replication. If two records only differ in their OID (or maybe
ctid?) value you will have problem.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-12-07 14:38:41 | Re: Logical replication without a Primary Key |
| Previous Message | Joshua D. Drake | 2017-12-07 14:32:58 | Re: Logical replication without a Primary Key |