Re: CREATE DATABASE vs delayed table unlink

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Matthew Wakeling <mnw21(at)cam(dot)ac(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: CREATE DATABASE vs delayed table unlink
Date: 2008-10-09 10:16:44
Message-ID: 48EDDA0C.2050705@enterprisedb.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Matthew Wakeling wrote:
> I could be wrong - but couldn't other bad things happen too? If you're
> copying the files before the checkpoint has completed, couldn't the new
> database end up with some of the recent changes going missing? Or is
> that prevented by FlushDatabaseBuffers?

FlushDatabaseBuffers prevents that.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-10-09 10:38:38 Re: CREATE DATABASE vs delayed table unlink
Previous Message Matthew Wakeling 2008-10-09 10:10:08 Re: CREATE DATABASE vs delayed table unlink