From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: It's past time to redo the smgr API |
Date: | 2004-02-05 21:22:41 |
Message-ID: | 12000.1076016161@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
> 'k, only comment is on this one ... would it not be a bit more efficient
> to add a flag to the "SMgrRelation *" structure that acts as a timer?
Hm, we could try that, although I'm not sure it would help much. You'd
have to set the timeout to be longer than a checkpoint interval to make
any difference.
In the back of my mind is the thought that the Windows guys are going to
end up passing file-delete requests over to the bgwriter anyway, which
would largely eliminate the issue --- the bgwriter would know which
files need to be sgmrclose'd and wouldn't have to do smgrcloseall.
(If they don't do this, how are they going to cope with backends that
exit before their file deletion is completed?)
I'll do it the easy way for now and we can refine it after we see what
the file-close solution for Windows ends up looking like.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2004-02-05 21:26:33 | Re: Preventing duplicate vacuums? |
Previous Message | Tom Lane | 2004-02-05 21:07:49 | Re: Preventing duplicate vacuums? |