Re: Template1 is locked when pgAdminIII is open

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 17:48:59
Message-ID: 20050131174859.GA9434@dcc.uchile.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

Hm, can we use LockSharedObject? It's on my shared dependency patch.

What needs to be locked? Maybe we need to take a AccessShareLock on the
pg_database row for schema changes, and AccessExclusiveLock on same for
database creation.

--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"La Primavera ha venido. Nadie sabe como ha sido" (A. Machado)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Steve Atkins 2005-01-31 17:54:24 Re: [BUGS] Bug in create operator and/or initdb
Previous Message Tom Lane 2005-01-31 17:29:12 Re: Template1 is locked when pgAdminIII is open