Skip site navigation (1) Skip section navigation (2)

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: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Bernd Helmle" <mailings(at)oopsware(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Reviewing temp_tablespaces GUC patch
Date: 2007-05-25 10:49:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 5/25/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jaime Casanova" <systemguards(at)gmail(dot)com> writes:
> > On 5/24/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> >> What happens if you create a cursor that stores something (sort
> >> intermediate results?) in a temp tablespace, FETCH some from it, then
> >> someone else drops the tablespace and FETCH some more?
> > you can't drop a tablespace that is not empty.
> So a temp file left over by a crashed backend would indefinitely prevent
> dropping the tablespace, until someone manually cleaned it up?

No, because the RemovePgTempFiles() call in PostmasterMain() will
remove all tmp files at startup.

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

In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-05-25 10:55:32
Subject: Re: like/ilike improvements
Previous:From: Zeugswetter Andreas ADI SDDate: 2007-05-25 08:16:59
Subject: Re: like/ilike improvements

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group