On Wed, Jan 12, 2005 at 09:17:33PM -0500, Tom Lane wrote:
> I notice that the backend seems to have been using some nonstandard C
> code:
>
> Error while reading shared library symbols:
> /home/markw/dbt2/storedproc/pgsql/c/../../../storedproc/pgsql/c/funcs.so: No
> such file or directory.
>
> W
Mark Wong <[EMAIL PROTECTED]> writes:
> Ok, well I got a core dump with 8.0rc4, but I'm not sure if it's
> exactly the same problem. I have the postgres binary and the core
> here:
> http://developer.osdl.org/markw/pgsql/core/2files.tar.bz2
> But it's for ia64, if you got one.
Poking around
On Tue, Dec 21, 2004 at 05:56:47PM -0500, Tom Lane wrote:
> If you want to track it yourself, please change those elog(ERROR)s to
> elog(PANIC) so that they'll generate core dumps, then build with
> --enable-debug if you didn't already (--enable-cassert would be good too)
> and get a debugger stack
Mark Wong wrote:
The overall throughput is better for a run like this:
http://www.osdl.org/projects/dbt2dev/results/dev4-010/207/
A drop from 3865 to 2679 (31%) by just adding pg_autovacuum. That's
what I meant by "not good". :)
I would agree that is "not good" :-) It sounds like pg_au
Mark Wong <[EMAIL PROTECTED]> writes:
> I was going to try Matthew's suggestion of turning up the debug on
> pg_autovacuum, unless you don't that'll help find the cause.
It won't help --- this is a backend-internal bug of some kind.
regards, tom lane
-
On Tue, Dec 21, 2004 at 05:56:47PM -0500, Tom Lane wrote:
> Mark Wong <[EMAIL PROTECTED]> writes:
> > On Tue, Dec 21, 2004 at 02:23:41PM -0500, Tom Lane wrote:
> >> Mark Wong <[EMAIL PROTECTED]> writes:
> >>> [2004-12-20 15:48:18 PST] The error is [ERROR: failed to
> >>> re-find parent k
Mark Wong <[EMAIL PROTECTED]> writes:
> On Tue, Dec 21, 2004 at 02:23:41PM -0500, Tom Lane wrote:
>> Mark Wong <[EMAIL PROTECTED]> writes:
>>> [2004-12-20 15:48:18 PST] The error is [ERROR: failed to re-find
>>> parent key in "pk_district"
>>
>> Yikes. Is this reproducible?
> Yes, and
The overall throughput is better for a run like this:
http://www.osdl.org/projects/dbt2dev/results/dev4-010/207/
A drop from 3865 to 2679 (31%) by just adding pg_autovacuum. That's
what I meant by "not good". :)
I'll start with the additional debug messages, with 8.0rc2, before
I start c
On Tue, Dec 21, 2004 at 02:23:41PM -0500, Tom Lane wrote:
> Mark Wong <[EMAIL PROTECTED]> writes:
> > [2004-12-20 15:48:18 PST] The error is [ERROR: failed to re-find
> > parent key in "pk_district"
> > ]
>
> Yikes. Is this reproducible?
>
> regards, tom lane
Ye
Mark Wong wrote:
After all this time I finally got around to vacuuming the database
with dbt2 with pg_autovacuum. :)
http://www.osdl.org/projects/dbt2dev/results/dev4-010/215/
Thanks!
Doesn't look so good though, probably because I'm not using optimal
settings with pg_autovacuum. So far I have
Mark Wong <[EMAIL PROTECTED]> writes:
> [2004-12-20 15:48:18 PST] The error is [ERROR: failed to re-find
> parent key in "pk_district"
> ]
Yikes. Is this reproducible?
regards, tom lane
---(end of broadcast)---
T
After all this time I finally got around to vacuuming the database
with dbt2 with pg_autovacuum. :)
http://www.osdl.org/projects/dbt2dev/results/dev4-010/215/
Doesn't look so good though, probably because I'm not using optimal
settings with pg_autovacuum. So far I have only tried the defa
12 matches
Mail list logo