Stephen Frost <sfr...@snowman.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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
