pg_sorttemp hits 2GB during index construction - Mailing list pgsql-hackers

From Martin Weinberg
Subject pg_sorttemp hits 2GB during index construction
Date
Msg-id 199912090406.XAA21251@osprey.astro.umass.edu
Whole thread Raw
Responses Re: [HACKERS] pg_sorttemp hits 2GB during index construction
List pgsql-hackers
I am trying to make an index on three columns (text, int2, date)
on a table with 193 million records.   I believe I am finding that
the pg_sorttemp files reach 2GB before the index finishes. 
The backend finishes the index but it's clearly missing tuples.

Does this make sense to you folks?

--Martin

P.S. My text field only contains a single char and I realize that
I was foolish not use a char(1) instead of varchar . . . 



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: [BUGS] uniqueness not always correct
Next
From: Don Baccus
Date:
Subject: Re: [HACKERS] Parallel regress tests (was Re: FOREIGN KEY andshift/reduce)