pgsql: Use a safer order of operations in dropdb(): rollbackable

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use a safer order of operations in dropdb(): rollbackable
Date: 2005-10-10 20:02:21
Message-ID: 20051010200221.84305D9E6B@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2005-10-10 22:29:49 pgsql: Remove the DELETEs from pg_shadow and pg_group that pg_dumpall
Previous Message Peter Eisentraut 2005-10-10 19:41:28 pgsql: Document the process to update translations.