| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | 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:32:58 |
| Message-ID: | 12b3ba82-f339-deac-06c7-fba4ca9171a1@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Thanks,
JD
>
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL Centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://pgconf.org
***** Unless otherwise stated, opinions are my own. *****
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-12-07 14:37:17 | Re: Logical replication without a Primary Key |
| Previous Message | Alexander Korotkov | 2017-12-07 13:38:59 | Re: Fwd: [BUGS] pg_trgm word_similarity inconsistencies or bug |