Postgres Pro
Downloads
Home   >   mailing lists

Re: including PID or backend ID in relpath of temp rels - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: including PID or backend ID in relpath of temp rels
Date
Msg-id y2u3073cc9b1004251919wcc0b3dd9rc8f2029f683245aa@mail.gmail.com
Whole thread Raw
In response to including PID or backend ID in relpath of temp rels  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: including PID or backend ID in relpath of temp rels  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
On Sun, Apr 25, 2010 at 8:07 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> 1. We could move the responsibility for removing the files associated
> with temp rels from the background writer to the owning backend.  I
> think the reason why we initially truncate the files and only later
> remove them is because somebody else might have 'em open, so it
> mightn't be necessary for temp rels.
>

what happens if the backend crash and obviously doesn't remove the
file associated with temp rels?

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: including PID or backend ID in relpath of temp rels
Next
From: Jaime Casanova
Date:
Subject: improve plpgsql's EXECUTE 'select into' message with a hint