Re: Why there are no max_wal_receivers

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: 高健 <luckyjackgao(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why there are no max_wal_receivers
Date: 2013-10-08 06:17:12
Message-ID: CA+HiwqEgorr8QUBN6brOKqNs0enMvVRkLGP273PibRNvBL9ZSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Oct 8, 2013 at 3:05 PM, 高健 <luckyjackgao(at)gmail(dot)com> wrote:
> Hello:
>
>
>
>
>
> Thank you all for kindly replying my question.
>
>
> I read the documentation about pg_basebackup.
>
>
> The description says:
>
> The server must also be configured with max_wal_senders set high enough to
> leave at least one session available for the backup.
>
> Dose it mean:
>
> If I am building a one master -- one slave environment, I need the
> max_wal_sender to be at least 2.
>
> But I think pg_basebackup just use the one sender process temporarily, Is
> that right?
>

Yes. It would be used for the duration of backup. But, it maybe better
to just reserve one slot for pg_basebackup if you intend to use it
often instead of editing postgresql.conf every time you need to take
backup.

--
Amit

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Toby Corkindale 2013-10-08 07:36:41 Many, many materialised views - Performance?
Previous Message 高健 2013-10-08 06:05:28 Re: Why there are no max_wal_receivers