Re: pg_autovacuum causes 'create database' to fail when the

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_autovacuum causes 'create database' to fail when the
Date: 2003-11-08 17:00:13
Message-ID: 12265.1068310813@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> ERROR: source database "template1" is being accessed by other users

> Good description --- not sure what we can do about it.

Sooner or later we'll have to face up to the conflict between using
template1 as the default createdb template and using it as the default
connection target for random scripts like createuser and autovacuum.

The interlock that tries to ensure we have a consistent state of
template1 on disk for createdb to copy is what creates the problem.
And it is not good enough anyway, since there's not any certainty that
someone couldn't connect to template1 and modify it while the 'cp -r'
is in progress.

I suspect ultimately we will have to abandon the use of 'cp -r' for
createdb and do it ourselves, internally. This may be forced by
tablespace disk-organization issues even before we think of a proper
solution to the interlock problem.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alex 2003-11-08 17:04:22 Help With date/time
Previous Message Rajesh Kumar Mallah 2003-11-08 17:00:04 Re: Service doesnt UP!!!!