| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Alfred Perlstein <alfred(at)freebsd(dot)org>, Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why we lost Uber as a user |
| Date: | 2016-08-03 19:15:54 |
| Message-ID: | 14878.1470251754@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> On 08/03/2016 11:23 AM, Tom Lane wrote:
>> I think the realistic answer if you suffer replication-induced corruption
>> is usually going to be "re-clone that slave", and logical rep doesn't
>> really offer much gain in that.
> Yes, it actually does. The ability to unsubscribe a set of tables,
> truncate them and then resubscribe them is vastly superior to having to
> take a base backup.
True, *if* you can circumscribe the corruption to a relatively small
part of your database, logical rep might provide more support for a
partial re-clone.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoff Winkless | 2016-08-03 19:31:49 | Re: Implementing full UTF-8 support (aka supporting 0x00) |
| Previous Message | Álvaro Hernández Tortosa | 2016-08-03 19:13:18 | Re: Implementing full UTF-8 support (aka supporting 0x00) |