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

Re: Reviewing temp_tablespaces GUC patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jaime Casanova" <systemguards(at)gmail(dot)com>
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 01:11:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"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?

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2007-05-25 01:26:19
Subject: Re: like/ilike improvements
Previous:From: Jaime CasanovaDate: 2007-05-25 00:04:01
Subject: Re: Reviewing temp_tablespaces GUC patch

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