Re: BUG #2631: database locking problem

The 8.1.4 shows POSTGIS="1.1.3" GEOS="2.2.1-CAPI-1.0.1" PROJ="Rel.
4.4.7, 31 March 2003" USE_STATS and the 8.1.3 shows POSTGIS="1.1.2"
GEOS="2.2.1-CAPI-1.0.1" PROJ="Rel. 4.4.7, 31 March 2003" USE_STATS

I've been playing with this a bit more by switching to 8.1.3 with
postgis 1.1.3 and still get the locking problem. I've attached a file
that shows the output of 'select pg_class.relname,pg_locks.* from
pg_class,pg_locks where pg_class.relfilenode=pg_locks.relation' and the
process list when it locks. I've also attached the table descriptions.

I'd really like to nail this as I have a production system going live
very soon (hopefully).

--
Ross Elliott
Senior Software Engineer
Infoterra Ltd
T +44 (0)1252 362095
www.infoterra.co.uk

-----Original Message-----
From: Michael Fuhr [mailto:mike(at)fuhr(dot)org]
Sent: 17 September 2006 14:41
To: Tom Lane
Cc: Ross Elliott; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #2631: database locking problem

On Sun, Sep 17, 2006 at 01:29:33AM -0400, Tom Lane wrote:
> "Ross Elliott" <ross(dot)elliott(at)infoterra-global(dot)com> writes:
> > So, what happened between 8.1.3 and 8.1.4 that may have affected
> > locking?
>
> Nothing that I know of. Please provide a self-contained test case
> (but are you sure this is not a PostGIS bug?) ...

What does "SELECT postgis_full_version()" show? If you still have the
8.1.3 system then please post the output from both 8.1.3 and 8.1.4.

--
Michael Fuhr