"mark" <dvlhntr(at)gmail(dot)com> writes:
> I don't know if this is a bug and if so, if it fixed in the most current
> patch. (I don't see anything in the release notes that make think so though
At least one reason for this type of problem was fixed in 8.4.
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Tue May 12 03:11:02 2009 +0000
Modify find_inheritance_children() and find_all_inheritors() to add the
ability to lock relations as they scan pg_inherits, and to ignore any
relations that have disappeared by the time we get lock on them. This
makes uses of these functions safe against concurrent DROP operations
on child tables: we will effectively ignore any just-dropped child,
rather than possibly throwing an error as in recent bug report from
Thomas Johansson (and similar past complaints). The behavior should
not change otherwise, since the code was acquiring those same locks
anyway, just a little bit later.
An exception is LockTableCommand(), which is still behaving unsafely;
but that seems to require some more discussion before we change it.
regards, tom lane
In response to
pgsql-novice by date
|Next:||From: Richard Broersma||Date: 2010-11-22 17:20:00|
|Subject: Re: Change Data Capture|
|Previous:||From: Tom Lane||Date: 2010-11-22 14:43:07|
|Subject: Re: Null values detected as 0 value |