| From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
|---|---|
| To: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: After an error - pg_replication_slot is dropped |
| Date: | 2018-02-16 16:04:33 |
| Message-ID: | 2a72d1a2-ca25-f349-a47f-98206a22fc2e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16/02/18 12:38, tushar wrote:
> On 02/16/2018 04:02 PM, Petr Jelinek wrote:
>> It's because you are creating temporary slot. Temporary slots are
>> removed on error, that's a documented behavior.
>
> Thanks for pointing out but It looks weird behavior - even a small mea
> culpa can remove the slot. Temporary table - doesn't go automatically
> after an error ?
>
Temporary tables have transactional properties, slots don't (even the
non-temporary). For example if you create replication slot in
transaction and then abort it, the slot will survive. That's the price
we pay for ability to create slots on standby.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-02-16 16:24:08 | Re: [HACKERS] [bug-fix] Cannot select big bytea values (~600MB) |
| Previous Message | Julian Markwort | 2018-02-16 15:45:28 | [PATCH] pg_hba.conf : new auth option : clientcert=verify-full |