Re: PG crash on simple query, story continues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Maksim Likharev" <mlikharev(at)aurigin(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PG crash on simple query, story continues
Date: 2003-07-08 05:14:25
Message-ID: 22581.1057641265@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Maksim Likharev" <mlikharev(at)aurigin(dot)com> writes:
> SELECT p.docid FROM prod.t_documents AS p
> INNER JOIN t_tempdocs AS t
> ON p.docid = t.docid
> LEFT OUTER JOIN prod.t_refs AS ct
> ON ct.docid = p.docid;

> here is a stack trace:
> 00252174 AllocSetAlloc (3813b0, 15, 251fe0, 20, 0, ffbee2f8) + 194
> 002532e4 MemoryContextAlloc (3813b0, 15, 11, 7efefeff, 81010100, ff00)
> + 68
> 0020dc0c varcharin (ffbee378, ffbee378, 20dae4, 0, 0, ffbee3f0) + 128
> 00243570 FunctionCall3 (ffbee4a8, 3c1ce8, 0, 324, 0, ffbee5c4) + 11c
> 0023e6c4 get_attstatsslot (3d6410, 413, 324, 2, 0, ffbee5c4) + 2b0
> 001f8cb4 scalarineqsel (3bb978, 42a, 0, 3bffa8, 40f0e8, 413) + 288
> 001fb824 mergejoinscansel (3bb978, 3c0080, 3c0968, 3c0970, 0, 1) + 23c

Hmm, it would seem there's something flaky about your pg_statistic
entries. Could we see the pg_stats rows for the columns mentioned
in this query?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Maksim Likharev 2003-07-08 05:16:24 Re: PG crash on simple query, story continues
Previous Message Andrew Sullivan 2003-07-08 05:05:20 Re: Website (DNS) is hosed!!!