pgsql: Lock database while running drop database in Hot Standby to

From: sriggs(at)postgresql(dot)org (Simon Riggs)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Lock database while running drop database in Hot Standby to
Date: 2010-01-16 14:16:31
Message-ID: 20100116141631.A609D7541B9@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message User Fxjr 2010-01-16 15:05:42 npgsql - Npgsql2: Added a test for Europe/Amsterdam timezone with dates
Previous Message User Maosen 2010-01-16 14:01:04 pgexternaltable - src: