Re: It's past time to redo the smgr API

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: It's past time to redo the smgr API
Date: 2004-02-05 23:24:43
Message-ID: 20040205192348.S4449@ganymede.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 5 Feb 2004, Tom Lane wrote:

> "Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
> > Why? Setting it to the checkpoint interval itself should be sufficient,
> > no? All you want to do is avoid closing any files that were used during
> > that last checkpoint interval, since there is a good chance you'd have to
> > once more reopen them in the checkpoint interval ...
>
> If we did that then (on Windows) every DROP TABLE would take one extra
> checkpoint interval to take effect in terms of freeing disk space.
> Not sure if this is a good tradeoff for avoiding some file opens.

k, but that would be a different scenario, no? As I mentioned in my
original, a DROP TABLE would reset its timeout to -1, meaning to close it
and drop it on the next checkpoint interval ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hans-Jürgen Schönig 2004-02-05 23:28:19 Re: Recursive queries?
Previous Message Tom Lane 2004-02-05 23:14:38 Re: It's past time to redo the smgr API