| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | 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-09 04:55:08 |
| Message-ID: | 12062.1357707308@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> If I can come up with a doc or similar patch, I'll post it, but I have
> to admit that the docs are pretty clear that you need create rights.
> Still, it seems a little odd that we don't complain in any way in this
> case. Perhaps a NOTICE when the temp_tablespaces value is set but won't
> be used due to permissions..?
The code definitely will complain if you try to interactively SET
temp_tablespaces to a space you lack permissions for. However, there
has never been a case in which people would hold still for warnings
emitted as a consequence of values read from postgresql.conf or other
background sources, and I doubt that the response would be different
if we made this variable act like that. See for example past
discussions about what to do with invalid entries in search_path.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-01-09 05:05:38 | Re: Index build temp files |
| Previous Message | Peter Eisentraut | 2013-01-09 04:49:49 | Re: Index build temp files |