Nico Sabbi wrote:
Merlin Moncure wrote:
try link mode, not copy mode (-l). make sure you read about the -k
switch.
merlin
replaced -c with -l, but the result was the same.
I assume that with -k you mean the socket dir for postgres - since
pg_standby doesn't
seek to recognize that switc
Merlin Moncure wrote:
try link mode, not copy mode (-l). make sure you read about the -k
switch.
merlin
replaced -c with -l, but the result was the same.
I assume that with -k you mean the socket dir for postgres - since
pg_standby doesn't
seek to recognize that switch - but I didn't ne
On 4/16/07, Nico Sabbi <[EMAIL PROTECTED]> wrote:
Merlin Moncure wrote:
> On 4/16/07, Nico Sabbi <[EMAIL PROTECTED]> wrote:
>
>> Is there any parameter that I have to pass to the second server to keep
>> on requesting WALs?
>> I still don't understand what instructs the server to continously
>>
Merlin Moncure wrote:
On 4/16/07, Nico Sabbi <[EMAIL PROTECTED]> wrote:
Is there any parameter that I have to pass to the second server to keep
on requesting WALs?
I still don't understand what instructs the server to continously
request the master's logs.
google pg_standby. I've set it up
On 4/16/07, Nico Sabbi <[EMAIL PROTECTED]> wrote:
Is there any parameter that I have to pass to the second server to keep
on requesting WALs?
I still don't understand what instructs the server to continously
request the master's logs.
google pg_standby. I've set it up and it works.
merlin
--
Tom Lane wrote:
Nico Sabbi <[EMAIL PROTECTED]> writes:
To begin with I followed the example of the docs: in the recovery.conf
file of the
slave instance I set
restore_command = 'cp -av /var/lib/pgsql/data/pg_xlog/%f %p'
Hm, it looks like you are trying to copy xlog segme
Nico Sabbi <[EMAIL PROTECTED]> writes:
> To begin with I followed the example of the docs: in the recovery.conf
> file of the
> slave instance I set
> restore_command = 'cp -av /var/lib/pgsql/data/pg_xlog/%f %p'
Hm, it looks like you are trying to copy xlog segments straight from the
pg_xlog d
