Skip site navigation (1) Skip section navigation (2)

pgsql: Improve sequence and sense of messages from pg_stop_backup().

From: sriggs(at)postgresql(dot)org (Simon Riggs)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve sequence and sense of messages from pg_stop_backup().
Date: 2010-04-18 18:44:53
Message-ID: 20100418184453.46C207541D0@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Improve sequence and sense of messages from pg_stop_backup().
Now doesn't report it is waiting until it actually is waiting,
plus message doesn't appear until at least 5 seconds wait, so
we avoid reporting the wait before we've given the archiver
a reasonable time to wake up and archive the file we just
created earlier in the function.
Also add new unconditional message to confirm safe completion.
Now a normal, healthy execution does not report waiting at
all, just safe completion.

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        xlog.c (r1.399 -> r1.400)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.399&r2=1.400)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-04-18 19:16:06
Subject: pgsql: Fix bogus order of cleanup steps in plperl_inline_handler.
Previous:From: Simon RiggsDate: 2010-04-18 18:17:12
Subject: pgsql: Remove some additional changes in previous commit that belong

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group