Re: Reviewing temp_tablespaces GUC patch
- From: "Jaime Casanova" <systemguards(at)gmail(dot)com>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "Bernd Helmle" <mailings(at)oopsware(dot)de>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Reviewing temp_tablespaces GUC patch
- Date: Fri, 25 May 2007 16:39:03 +0000
- Message-id: <c2d9e70e0705250939o19e48f2fg9f912c4634c95b0f(at)mail(dot)gmail(dot)com>
On 5/25/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
Bernd Helmle <mailings(at)oopsware(dot)de> writes:
> --On Freitag, Mai 25, 2007 10:49:29 +0000 Jaime Casanova
> <systemguards(at)gmail(dot)com> wrote:
>> No, because the RemovePgTempFiles() call in PostmasterMain() will
>> remove all tmp files at startup.
I believe we do not call RemovePgTempFiles during a crash recovery
cycle; this is intentional on the theory that the temp files might contain
useful debugging clues.
ah, i forgot that
So there is a potential problem there.
Not sure how important it really is though --- neither crashes nor
tablespace drops ought to be so common that we need a really nice
solution.
the only semi-sane solution i can think of, is to have a superuser
only function that acts as a wrapper for RemovePgTempFiles(), but
still exists a chance for shoot yourself on the foot...
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook
Home |
Main Index |
Thread Index