pgsql: Use a safer order of operations in dropdb(): rollbackable - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Use a safer order of operations in dropdb(): rollbackable
Date
Msg-id 20051010200221.84305D9E6B@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Use a safer order of operations in dropdb(): rollbackable operations,
ie removing shared-dependency entries, should happen before non-rollbackable
ones.  That way a failure during the rollbackable part doesn't leave us
with inconsistent state.

Modified Files:
--------------
    pgsql/src/backend/commands:
        dbcommands.c (r1.171 -> r1.172)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c.diff?r1=1.171&r2=1.172)

pgsql-committers by date:

Previous
From: petere@svr1.postgresql.org (Peter Eisentraut)
Date:
Subject: pgsql: Document the process to update translations.
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Remove the DELETEs from pg_shadow and pg_group that pg_dumpall