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

From Robert Haas
Subject Re: including PID or backend ID in relpath of temp rels
Date
Msg-id u2w603c8f071005041534v84afe6b1w3e11b0fd48ec5d0c@mail.gmail.com
Whole thread Raw
In response to Re: including PID or backend ID in relpath of temp rels  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, May 4, 2010 at 5:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> One possible thing we might do (bearing in mind that we might need to
>> wall off access at multiple levels) would be to forbid creating a
>> relcache entry for a non-local temprel.  That would, in turn, forbid
>> doing pretty much anything to such a relation, although I'm not sure
>> what else would get broken in the process.
>
> Dropping temprels left behind by a crashed backend would get broken by
> that; which is a deal-breaker, because we have to be able to clean those
> up.

Phooey.  It was such a good idea in my head.

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: including PID or backend ID in relpath of temp rels
Next
From: Tom Lane
Date:
Subject: Re: max_standby_delay considered harmful