On Thu, Feb 05, 2004 at 04:55:44PM -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> > Another way to do it would be keeping the list of files to delete along
> > with the deleting Xid, but that would also require keeping a list of
> > which xacts aborted and which ones didn't.
>
> Really? When a subtransaction finishes, you either delete its files
> immediately (ie, if it aborted, you can drop files it created) or you
> reassign them as the responsibility of the parent (since any effects of
> the subtransaction really depend on whether the parent commits, you
> can't actually do its deletes yet).
Right, that's the mechanism I originally envisioned. (A similar one is
needed for deferred triggers, async notifies, heavy locks and on commit
actions.)
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
Y dijo Dios: "Que sea Satanás, para que la gente no me culpe de todo a mí."
"Y que hayan abogados, para que la gente no culpe de todo a Satanás"
