From: | Poul Kristensen <bcc5226(at)gmail(dot)com> |
---|---|
To: | |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: recovery.conf |
Date: | 2016-09-06 09:53:58 |
Message-ID: | CAAOuvVqGvtLaZujiJ12OmT78YMzk2TpUQfyX5uzzm4_LeaCTJQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Sorry for asking a lot.
pg_replication_slots.
is this meant to be a slot like a ethernetcard and controller in a physical
server.
Thanks a lot.
/Poul
2016-09-06 10:41 GMT+02:00 Poul Kristensen <bcc5226(at)gmail(dot)com>:
> Thanks a lot for fast responce.
>
> Do you have any idea of why PostgreSQL don't use cluster like normally
> used e.g
> One common disk for both master and nodes?
>
> Thanks.
>
> Poul
>
> 2016-09-05 14:24 GMT+02:00 Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>:
>
>> Poul Kristensen wrote:
>> > It is not obvious to me what is the minimum configuration of the
>> recovery.conf?
>> >
>> > The online manuals does not give the exact minumum.
>> >
>> > Can anyone help?
>>
>> None of the settings in recovery.conf must be specified.
>>
>> One that you will almost always have for recovery is "restore_command",
>> but if all
>> the WAL you need is in pg_xlog, you don't have to specify that either.
>> And you don't need it for streaming replication.
>>
>> Some settings are necessary for point-in-time-recovery, and some
>> for streaming replication, which are two different use cases for the same
>> recovery mechanism.
>> Maybe that's what's confusing you.
>>
>> Yours,
>> Laurenz Albe
>>
>
>
>
> --
> Med venlig hilsen / Best regards
> Poul Kristensen
> Linux-OS/Virtualizationexpert and Oracle DBA
>
--
Med venlig hilsen / Best regards
Poul Kristensen
Linux-OS/Virtualizationexpert and Oracle DBA
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2016-09-06 12:13:58 | Re: recovery.conf |
Previous Message | Poul Kristensen | 2016-09-06 08:41:39 | Re: recovery.conf |