pgsql: Simplify relcache startup sequence. - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Simplify relcache startup sequence.
Date
Msg-id 20060504185136.230B49FA65C@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Simplify relcache startup sequence.  With the new design of InitPostgres
it's not necessary to have three separate calls anymore.  This patch also
fixes things so we don't try to read pg_internal.init until after we've
obtained lock on the target database; which was fairly harmless, but it's
certainly cleaner this way.

Modified Files:
--------------
    pgsql/src/backend/utils/cache:
        relcache.c (r1.239 -> r1.240)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/relcache.c.diff?r1=1.239&r2=1.240)
    pgsql/src/backend/utils/init:
        postinit.c (r1.166 -> r1.167)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/postinit.c.diff?r1=1.166&r2=1.167)
    pgsql/src/include/utils:
        relcache.h (r1.53 -> r1.54)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/relcache.h.diff?r1=1.53&r2=1.54)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Rethink the locking mechanisms used for CREATE/DROP/RENAME
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Code review for contrib/pg_freespacemap.