pgsql: Make LockDatabaseObject() AcceptInvalidationMessages(). - Mailing list pgsql-committers

From rhaas@postgresql.org (Robert Haas)
Subject pgsql: Make LockDatabaseObject() AcceptInvalidationMessages().
Date
Msg-id 20100816020228.865337541D7@cvs.postgresql.org
Whole thread Raw
Responses Re: pgsql: Make LockDatabaseObject() AcceptInvalidationMessages().  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-committers
Log Message:
-----------
Make LockDatabaseObject() AcceptInvalidationMessages().

This is appropriate for the same reasons we already do it in
LockSharedObject(): things might have changed while we were waiting
for the lock.  There doesn't seem to be a live bug here at the moment,
but that's mostly because it isn't currently used for very much.

Modified Files:
--------------
    pgsql/src/backend/storage/lmgr:
        lmgr.c (r1.100 -> r1.101)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lmgr.c?r1=1.100&r2=1.101)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix psql's copy of utf2ucs() to match the backend's copy exactly;
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Arrange to fsync the contents of lockfiles (both postmaster.pid