Re: pgsql: Add support for temporary replication slots

From: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add support for temporary replication slots
Date: 2016-12-13 01:21:27
Message-ID: 495584eb-c8c8-90ba-0e21-1b0ecc148bf4@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 13/12/16 02:08, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2016-12-13 01:57:01 +0100, Petr Jelinek wrote:
>>> I mentioned that as possible solution upthread, I am only worried that
>>> the failure scenario is basically infinite loop.
>
>> I don't see the problem with that. If you're really concerned you can
>> set a statement timeout.
>
> I don't think "change the test" is the right response here.
> I think the problem is that we're disconnecting from the slot at the
> wrong step of backend shutdown, and that we need to fix that before
> it bites us on some more painful parts of our anatomies. You can't
> just throw darts at the code when deciding where to do things, and
> proc.c is NOT the place that should be concerned with replication
> slots.
>

It has been concerned with replication slots since 9.4 so it's not like
it's newly invented concern. As Andres says, we don't have better place
to put it to at the moment.

--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Petr Jelinek 2016-12-13 01:28:26 Re: pgsql: Add support for temporary replication slots
Previous Message Andres Freund 2016-12-13 01:11:01 Re: pgsql: Add support for temporary replication slots

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2016-12-13 01:23:16 Re: pg_background contrib module proposal
Previous Message Amit Langote 2016-12-13 01:17:30 Re: Declarative partitioning - another take