Re: pgsql: Add support for temporary replication slots

From: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:28:26
Message-ID: a6b63bc4-ed38-2908-ef8d-1d96f2012d57@2ndquadrant.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 13/12/16 02:00, Andres Freund wrote:
> 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.
>

Okay in case we decide it's the right way to go attached patch does
that. I also added some more tests based on your feedback while I am at it.

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

Attachment Content-Type Size
0001-Various-temporary-slots-test-improvements.patch text/x-diff 7.2 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Langote 2016-12-13 04:06:15 Re: pgsql: Fix creative, but unportable, spelling of "ptr != NULL".
Previous Message Petr Jelinek 2016-12-13 01:21:27 Re: pgsql: Add support for temporary replication slots

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2016-12-13 01:32:22 Re: PATCH: two slab-like memory allocators
Previous Message Craig Ringer 2016-12-13 01:27:12 Re: background sessions