| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2013-01-10 02:45:36 | Re: lazy_vacuum_heap()'s removal of HEAPTUPLE_DEAD tuples |
| Previous Message | Bruce Momjian | 2013-01-10 02:22:48 | Lock levels for ALTER TABLE |