|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|To:||Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>|
|Cc:||Sergei Kornilov <sk(at)zsrv(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: base backup client as auxiliary backend process|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Fri, Nov 22, 2019 at 11:21:53AM +0100, Peter Eisentraut wrote:
> After thinking about this a bit more, doing the temporary slot stuff on the
> walsender side might lead to too many complications in practice.
> Here is another patch set that implements the temporary slot use on the
> walreceiver side, essentially mirroring what pg_basebackup already does.
I have not looked at the patch, but controlling the generation of the
slot from the client feels much more natural to me. This reuses the
existing interface, which is consistent, and we avoid a new class of
bugs if there is any need to deal with the cleanup of the slot on the
WAL sender side it itself created.
|Next Message||Etsuro Fujita||2019-11-22 13:08:15||Re: [HACKERS] advanced partition matching algorithm for partition-wise join|
|Previous Message||Michael Paquier||2019-11-22 12:22:10||Re: obsolete example|