From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: thousand unrelated data files in pg_default tablespace |
Date: | 2010-09-03 11:00:31 |
Message-ID: | 4C80D54F.4060003@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 03/09/10 11:16, Pavel Stehule wrote:
> 2010/8/31 Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Pavel Stehule<pavel(dot)stehule(at)gmail(dot)com> writes:
>>> there is a dump from 8KB files
>>
>> Well, those certainly look like tables/indexes not temp files.
>> So we can rule out one theory.
>>
>> You're *certain* these aren't referenced from pg_class.relfilenode
>> of any of the databases in the server?
>
> I have a info, so these files are not in pg_class.relfilenode. More -
> these files are three months old, and in this time was server two
> times restarted.
Maybe they're tables that were created in a transaction, but the process
crashed hard before committing? Like:
BEGIN;
CREATE TABLE foo (...);
COPY foo FROM ...;
kill -9 postgres
That will leave behind a file like that. Do you do something like that
in the application?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-09-03 11:19:20 | Streaming a base backup from master |
Previous Message | Heikki Linnakangas | 2010-09-03 10:50:54 | Re: Interruptible sleeps (was Re: CommitFest 2009-07: Yay, Kevin! Thanks, reviewers!) |