| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
| 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:00:59 |
| Message-ID: | 20161213010059.dn64rrb3u7zxnnwk@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-13 01:08:01 | Re: pgsql: Add support for temporary replication slots |
| Previous Message | Petr Jelinek | 2016-12-13 00:57:01 | Re: pgsql: Add support for temporary replication slots |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-12-13 01:05:12 | Re: exposing wait events for non-backends (was: Tracking wait event for latches) |
| Previous Message | Petr Jelinek | 2016-12-13 00:57:01 | Re: pgsql: Add support for temporary replication slots |