From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Mehul Doshi-A20614 <mehul(at)motorola(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Template1 is locked when pgAdminIII is open |
Date: | 2005-01-31 18:04:21 |
Message-ID: | 21067.1107194661@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> On Mon, Jan 31, 2005 at 12:29:12PM -0500, Tom Lane wrote:
>> Of course, sooner or later we should fix the underlying locking
>> mechanism so we don't have to have this constraint, but I'm not sure
>> when that will happen.
> What needs to be locked?
Somehow we'd need to prevent any changes to the template database while
it's being copied. AFAICS this would require something on the order of
taking out a lock at the database level for every query, which sounds
like a mighty expensive solution compared to the seriousness of the
problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2005-01-31 18:04:55 | Re: Template1 is locked when pgAdminIII is open |
Previous Message | Steve Atkins | 2005-01-31 17:54:24 | Re: [BUGS] Bug in create operator and/or initdb |