Skip site navigation (1) Skip section navigation (2)

Re: ERROR: tuple concurrently updated

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: ERROR: tuple concurrently updated
Date: 2006-12-21 15:52:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > I havn't built a reliable test case yet but I *think* the tuple
> > concurrently updated problem is with an analyze being run inside of a
> > function and also being run by autovacuum.
> If so it should be fixed as of 8.2 --- I believe we changed the locking
> rules to ensure only one ANALYZE at a time for any one table.
> I think we've got a solution for that in 8.2, also --- at least, the
> only common case I know of should be fixed, namely where a RENAME or
> similar has caused the same table name to be assigned to a new OID.

Great!  These were on 8.1 and I was actually just working to try and
reproduce them on 8.2 (without success so far!).  I'll see about
upgrading the production systems to 8.2 soon and will let ya'll know if
I see them again there.



In response to

pgsql-hackers by date

Next:From: Dave PageDate: 2006-12-21 15:57:34
Subject: Re: Interface for pg_autovacuum
Previous:From: Tom LaneDate: 2006-12-21 15:50:59
Subject: Re: column ordering, was Re: [PATCHES] Enums patch v2

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group