| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | andres(at)anarazel(dot)de |
| Cc: | craig(at)2ndquadrant(dot)com, peter(dot)eisentraut(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: REPLICA IDENTITY FULL |
| Date: | 2017-06-20 02:52:10 |
| Message-ID: | 20170620.115210.1557964264725915001.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> For example, if the table consists of only INT types, REPLICA IDENTITY
>> FULL works with UPDATE/DELETE (i.e. replicated), but if some of them
>> are TEXT types, then UPDATE/DELETE does not work.
>>
>> See up thread for more details.
>
> Right, but that's just a bug, nothing else.
If my understanding is correct, it would not be easy to fix, no?
> 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.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-06-20 02:54:41 | Re: Get stuck when dropping a subscription during synchronizing table |
| Previous Message | Andres Freund | 2017-06-20 02:47:06 | Re: REPLICA IDENTITY FULL |