From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ryan D(dot) Enos" <renos(at)ucla(dot)edu> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: large duplicated files |
Date: | 2007-08-17 13:53:18 |
Message-ID: | 4653.1187358798@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
"Ryan D. Enos" <renos(at)ucla(dot)edu> writes:
> My problem is that my database is creating large duplicate
> files, i.e.: 17398.1, 17398.2, 17398.3, etc. Each is about 1g in size.
These are not "duplicates", they are sections of a very large table
(or possibly a very large index).
I gather from your followup that the files are now gone, meaning that
someone dropped the table. If they were still there you could determine
which table they belonged to by looking at pg_class.relfilenode --- see
http://www.postgresql.org/docs/8.2/static/storage.html
for information about the physical layout of a PG database.
My best guess about what happened is that a client did something like
CREATE TEMP TABLE foo AS SELECT ...
with an erroneous query that generated a huge table --- maybe it had
a missing join condition or something like that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Monarchi | 2007-08-17 15:48:02 | ERROR: relation with OID XXXX does not exist |
Previous Message | Christoph Frick | 2007-08-17 08:37:07 | Re: large duplicated files |