Re: Don'st start streaming after creating a slot in pg_receivexlog

From: Andres Freund <andres(at)anarazel(dot)de>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Don'st start streaming after creating a slot in pg_receivexlog
Date: 2015-07-29 10:41:36
Message-ID: 20150729104136.GA10043@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-07-29 09:23:43 +0100, Simon Riggs wrote:
> Creating a temporary slot goes against the whole concept of slots, so using
> the same id in the same script isn't actually needed, except maybe to
> simplify testing.

The concept of a slot is to reserve resources. I don't see why it's
wrong to reserve resources temporarily.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-07-29 10:43:53 Re: pg_basebackup and replication slots
Previous Message Dean Rasheed 2015-07-29 09:41:34 Re: more RLS oversights