Re: BUG #2225: Backend crash -- BIG table

From: Patrick Rotsaert <patrick(dot)rotsaert(at)arrowup(dot)be>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2225: Backend crash -- BIG table
Date: 2006-02-03 17:18:44
Message-ID: 43E39074.1010506@arrowup.be
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


>One question is what does the explain (without analyze) plan look like for
>the above and are the row estimates valid in the case of one of the hash
>plans.
>
>
pointspp=# explain select trid, count(*) from pptran group by trid
having count(*) > 1;
QUERY PLAN
--------------------------------------------------------------------------
HashAggregate (cost=1311899.28..1311902.78 rows=200 width=18)
Filter: (count(*) > 1)
-> Seq Scan on pptran (cost=0.00..1039731.02 rows=36289102 width=18)
(3 rows)

>Failing that, how many rows should the above return?
>
>
That is exactly what I am trying to find out. I can only guess that, but
it should not be more than a couple of 10k rows.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephan Szabo 2006-02-03 17:34:49 Re: BUG #2225: Backend crash -- BIG table
Previous Message Patrick Rotsaert 2006-02-03 17:15:42 Re: BUG #2225: Backend crash -- BIG table