Re: CREATE DATABASE fails when template1 being accessed ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)surnet(dot)cl>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: CREATE DATABASE fails when template1 being accessed ...
Date: 2005-05-31 20:28:56
Message-ID: 23254.1117571336@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)surnet(dot)cl> writes:
> On Tue, May 31, 2005 at 02:49:09PM -0400, Tom Lane wrote:
>> It's a rather lame attempt to ensure that you don't get a corrupt copy
>> due to the database changing while you copy it ... I'd like to find
>> a better way to do it ...

> You sounded less enthusiastic about it on january:
> http://archives.postgresql.org/pgsql-bugs/2005-01/msg00395.php

Well, I was expressing dissatisfaction with the obvious way of fixing
it. If we knew a low-overhead way to fix it I'd be much more
enthusiastic ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2005-05-31 20:55:29 Tablespace-level Block Size Definitions
Previous Message Tom Lane 2005-05-31 20:26:20 Quick-and-dirty compression for WAL backup blocks