| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: REPLICA IDENTITY FULL |
| Date: | 2017-06-19 22:53:25 |
| Message-ID: | 9f5c58e2-6f07-8b3b-9241-821c61c7e9a9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/18/17 23:11, Tatsuo Ishii wrote:
> While playing around with logical replication, I am confused by the
> behavior of REPLICA IDENTITY FULL.
> However, if a table has text columns, UPDATE/DELETE replication does
> not work any more. Am I missing something?
This is apparently because for replica identity full the comparison of
the search key against the tuple value goes through datumIsEqual(),
which doesn't work for TOAST values.
We might be able to refine that, but there is a general problem that
without an index and an operator class, we are just doing our random
best to match the values.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2017-06-19 23:33:31 | Re: REPLICA IDENTITY FULL |
| Previous Message | Andres Freund | 2017-06-19 22:49:38 | Re: PATCH: Batch/pipelining support for libpq |