On Mon, Apr 12, 2010 at 8:32 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Mon, Apr 12, 2010 at 11:27 PM, Jaime Casanova
> <jcasanov(at)systemguards(dot)com(dot)ec> wrote:
>>> 1. start the primary
>>> 2. pg_start_backup()
>>> 3. copy $PGDATA from the primary to the standby
>>> 4. pg_stop_backup();
>>> 5. create the recovery.conf and start the standby
>> execute some WAL-logged action (i've seen this happen even with no
>> WAL-logged action if i wait for a while before shutdown servers)
>>> 6. shutdown (smart mode) the standby
>> shutdown (smart) the primary
>> start the primary again
>>> 7. start the standby again
>>> --> cannot accept connnections until new WAL has been created
> I was not able to reproduce the problem using the above scenario.
> But when I did one more restart of the primary and standby, I was
> able to observe the problem. If this is the same as you encountered,
> it would be the "can't start hot standby from a shutdown checkpoint"
> issue that Heikki pointed out. So it's very helpful to check whether
> the posted patch fixes your problem or not.
this patch seems to fix the problem for me...
i will read it on the morning and the thread where it is, something
that seems strange to me is that the patch touch twophase.c and
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2010-04-13 06:15:25|
|Subject: Re: Naming of new EXCLUDE constraints |
|Previous:||From: Tom Lane||Date: 2010-04-13 06:09:28|
|Subject: Re: non-reproducible failure of random test on HEAD |