pgsql: Lock database while running drop database in Hot Standby to - Mailing list pgsql-committers

From sriggs@postgresql.org (Simon Riggs)
Subject pgsql: Lock database while running drop database in Hot Standby to
Date
Msg-id 20100116141631.A609D7541B9@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Lock database while running drop database in Hot Standby to protect
against concurrent reconnection. Failure during testing showed issue
was possible, even though earlier analysis seemed to indicate it
would not be required. Use LockSharedObjectForSession() before
ResolveRecoveryConflictWithDatabase() and hold lock until end of
processing for that WAL record. Simple approach to avoid introducing
further bugs at this stage of development on an improbable issue.

Modified Files:
--------------
    pgsql/src/backend/commands:
        dbcommands.c (r1.232 -> r1.233)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c?r1=1.232&r2=1.233)

pgsql-committers by date:

Previous
From: maosen@pgfoundry.org (User Maosen)
Date:
Subject: pgexternaltable - src:
Next
From: fxjr@pgfoundry.org (User Fxjr)
Date:
Subject: npgsql - Npgsql2: Added a test for Europe/Amsterdam timezone with dates