pgsql: Force a checkpoint in CREATE DATABASE before starting to copy the

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Force a checkpoint in CREATE DATABASE before starting to copy the
Date: 2008-10-09 10:34:22
Message-ID: 20081009103422.D8F257545A4@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Force a checkpoint in CREATE DATABASE before starting to copy the files,
to process any pending unlinks for the source database.

Before, if you dropped a relation in the template database just before
CREATE DATABASE, and a checkpoint happened during copydir(), the checkpoint
might delete a file that we're just about to copy, causing lstat() in
copydir() to fail with ENOENT.

Backpatch to 8.3, where the pending unlinks were introduced.

Per report by Matthew Wakeling and analysis by Tom Lane.

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
pgsql/src/backend/commands:
dbcommands.c (r1.204.2.3 -> r1.204.2.4)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c?r1=1.204.2.3&r2=1.204.2.4)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-10-09 15:49:04 pgsql: Fix crash in bytea-to-XML mapping when the source value is
Previous Message Heikki Linnakangas 2008-10-09 10:34:06 pgsql: Force a checkpoint in CREATE DATABASE before starting to copy the