From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Abhinav Singh <abhinav(dot)thegame(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Logical Replication - test_decoding - unchanged-toast-datum |
Date: | 2017-09-28 00:19:08 |
Message-ID: | CAMsr+YHJX8PXMwNPzxxWKsaU+n9WmB=6RD0g_gJhQy7hy1KQ8g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 26 September 2017 at 05:01, Abhinav Singh <abhinav(dot)thegame(at)gmail(dot)com>
wrote:
> Hello,
>
> I am currently using PostgreSQL Community version 9.4.9 and then using
> this instance, I am doing logical replication(using replication slots). I
> have created the replication slots using the following query:
>
> SELECT xlog_position FROM pg_create_logical_replication_
> slot('cjkimqvfuvixqyjd_00016389_e6f7c975_a311_4067_bcf1_a6accb57ab37',
> 'test_decoding')
>
> ...
> 3. So now I started my replication.
>
>
This is one of the MANY reasons test_decoding isn't suitable as the base
for a replication solution. It has "test" in its name for a reason.
Your replication model, whatever it is, is broken, since it's not handling
special cases like unchanged TOASTed values in UPDATEs. This is a bug in
your replication tool.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-09-28 02:08:08 | Re: Logical Replication - test_decoding - unchanged-toast-datum |
Previous Message | Scott Mead | 2017-09-27 20:10:45 | Re: Rsync to a recovering streaming replica? |