Re: BUG #2225: Backend crash -- BIG table - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2225: Backend crash -- BIG table
Date
Msg-id 28099.1138992631@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2225: Backend crash -- BIG table  ("Patrick Rotsaert" <patrick.rotsaert@arrowup.be>)
List pgsql-bugs
Patrick Rotsaert <patrick.rotsaert@arrowup.be> writes:
> I did a vacuum analyze, now the explain gives different results.

> pointspp=# explain select trid, count(*) from pptran group by trid
> having count(*) > 1;
>                                    QUERY PLAN
> --------------------------------------------------------------------------------
>  GroupAggregate  (cost=9842885.29..10840821.57 rows=36288592 width=18)
>    Filter: (count(*) > 1)
>    ->  Sort  (cost=9842885.29..9933606.77 rows=36288592 width=18)
>          Sort Key: trid
>          ->  Seq Scan on pptran  (cost=0.00..1039725.92 rows=36288592
> width=18)
> (5 rows)

OK that looks more reasonable.

> pointspp=# select trid, count(*) from pptran group by trid having
> count(*) > 1;
> ERROR:  could not write block 661572 of temporary file: No space left on
> device
> HINT:  Perhaps out of disk space?

> I have 5.1GB of free disk space. If this is the cause, I have a
> problem... or is there another way to extract (and remove) duplicate rows?

Time to buy more disk :-(

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2225: Backend crash -- BIG table
Next
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] Problems building pg 8.1.1