| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: File leak? |
| Date: | 2004-06-12 18:38:29 |
| Message-ID: | 200406121838.i5CIcT208773@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> > I wonder if we could clean up those lost files on database recovery or
> > vacuum.
>
> There is a TODO for this, but it seems exceedingly low priority to me.
>
> In any case I'd not recommend troubling to work on the problem until
> the tablespaces merry-go-round comes to a complete stop, since that
> restructuring will likely change what you'd need to do to identify
> unreferenced files.
Agreed on the need to wait until after tablespaces. I have an old patch
that does lookups on postmaster start to check for unreferenced files,
but it wasn't perfect.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2004-06-12 18:54:23 | Re: Why frequently updated tables are an issue |
| Previous Message | Carl E. McMillin | 2004-06-12 18:24:44 | Re: I just got it: PostgreSQL Application Server -- a new project. |