Re: pg_basebackup --slot=SLOTNAME -X stream

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_basebackup --slot=SLOTNAME -X stream
Date: 2014-03-18 13:32:32
Message-ID: 53284AF0.1090301@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/18/2014 03:25 PM, Fujii Masao wrote:
> Hi,
>
> Is there the explicit reason why --slot option that pg_receivexlog
> already has has not been added into pg_basebackup? If not,
> I'd like to support that option to eliminate the need to increase
> wal_keep_segments for pg_basebackup. Thought?

That seems rather cumbersome. pg_basebackup is a run once, and then it
dies. The slot would have to be created before running pg_basebackup,
and destroyed manually.

It would make sense to provide a new option that would tell the server
to recycle segments until they've been sent to this client, or until the
client disconnects. But that would look quite different from
pg_receivexlog's --slot option.

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2014-03-18 13:46:59 Re: pg_basebackup --slot=SLOTNAME -X stream
Previous Message Andres Freund 2014-03-18 13:31:08 Re: pg_basebackup --slot=SLOTNAME -X stream