pg_sorttemp hits 2GB during index construction

From: Martin Weinberg <weinberg(at)osprey(dot)astro(dot)umass(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Cc: weinberg(at)osprey(dot)astro(dot)umass(dot)edu
Subject: pg_sorttemp hits 2GB during index construction
Date: 1999-12-09 04:06:01
Message-ID: 199912090406.XAA21251@osprey.astro.umass.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 . . .

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 1999-12-09 04:30:30 Re: [HACKERS] Parallel regress tests (was Re: FOREIGN KEY andshift/reduce)
Previous Message Jan Wieck 1999-12-09 03:57:00 Re: [HACKERS] Parallel regress tests (was Re: FOREIGN KEY andshift/reduce)