Great! Is background writer clogging worthy? That's the one that put
postgres in a nearly unusable state after this bug was tripped.
Thanks!
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue
Thomas F. O'Connell [EMAIL PROTECTED] writes:
Tom seems to come pretty close to a TODO item in his analysis in my
opinion. Something like:
Make the planner ignore temp tables of other backends when expanding
an inheritance list.
I've done this in CVS tip. I'm not sure whether it should
Added to TODO:
* Prevent inherited tables from expanding temporary subtables of other
sessions
---
Thomas F. O'Connell wrote:
On Jul 21, 2005, at 1:22 PM, Bruce Momjian wrote:
Thomas F. O'Connell
Thomas F. O'Connell wrote:
I'm switching the aftermath of this thread -- http://
archives.postgresql.org/pgsql-general/2005-07/msg00501.php -- to -
hackers since it raised issues of potential concern to developers.
At various points in the thread, Tom Lane said the following:
I have an
On Jul 21, 2005, at 1:22 PM, Bruce Momjian wrote:
Thomas F. O'Connell wrote:
I'm switching the aftermath of this thread -- http://
archives.postgresql.org/pgsql-general/2005-07/msg00501.php -- to -
hackers since it raised issues of potential concern to developers.
At various points in the
I'm switching the aftermath of this thread -- http://archives.postgresql.org/pgsql-general/2005-07/msg00501.php -- to -hackers since it raised issues of potential concern to developers.At various points in the thread, Tom Lane said the following:"I have an old note to myself that persistent write
