| From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical replication without a Primary Key |
| Date: | 2017-12-07 14:43:08 |
| Message-ID: | 786d987f-97f3-037d-b4e5-b9e30fcc8487@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/12/17 15:32, Joshua D. Drake wrote:
> On 12/07/2017 05:30 AM, Peter Eisentraut 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.
>
> Thanks Peter, Craig also responded,
>
> The confusion I have is what if we have two rows that are identical and
> now that I think about it we would just update both rows, yes? That
> would make sense because it would produce two updated rows.
>
No it won't, it will update only one row, it does not try to find
multiple matching rows.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-12-07 14:56:33 | Re: Postgres with pthread |
| Previous Message | Craig Ringer | 2017-12-07 14:38:41 | Re: Logical replication without a Primary Key |