Re: Index build temp files

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index build temp files
Date: 2013-01-10 09:48:23
Message-ID: CA+U5nM+hyuVb71r=qqZWhF6u5X0_Mk2fg9PQ670H8te+bx2hdg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10 January 2013 04:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> Having it USERSET allows different settings for different roles, which
>> is useful.
>
> That would still be possible if it were SUSET; you'd just need a
> superuser to set it for you (via ALTER ROLE SET, or perhaps a
> security-definer wrapper function if you were desperate).
>
> The real question is how necessary is it for unprivileged code to set
> temp_tablespaces *for itself*. I doubt that that's all that critical.

OK, I can accept that

> I suspect the variable is hardly used in the field at all, given that
> it's been there since 8.3 and nobody noticed these issues until
> Stephen started poking at it.

...just not that bit, since it was not being used as documented.

> Note I am certainly not suggesting that we back-patch any such change.
> This would just be for 9.3 and up. We have surely made bigger
> incompatible changes than this one, probably in just about every major
> release.

OK

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-01-10 09:55:20 Re: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)
Previous Message Andres Freund 2013-01-10 09:31:04 Re: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)