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

Re: Index build temp files

From: Noah Misch <noah(at)leadboat(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Simon Riggs <simon(at)2ndQuadrant(dot)com>,Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index build temp files
Date: 2013-01-10 02:36:55
Message-ID: 20130110023655.GB11600@tornado.leadboat.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Jan 09, 2013 at 03:20:33PM -0500, Tom Lane wrote:
> What would people think of just eliminating the access-permissions
> checks involved in temp_tablespaces?  It would likely be appropriate to
> change temp_tablespaces from USERSET to SUSET if we did so.  So
> essentially the worldview would become that the DBA is responsible for
> the temp_tablespaces setting, not individual users.

Allowing that the new behavior could be clearer, that gain is too small to
justify the application compatibility hazard of making temp_tablespaces SUSET.
I don't see something we can do here that clearly improves things overall.


In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2013-01-10 02:45:36
Subject: Re: lazy_vacuum_heap()'s removal of HEAPTUPLE_DEAD tuples
Previous:From: Bruce MomjianDate: 2013-01-10 02:22:48
Subject: Lock levels for ALTER TABLE

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