Heikki Linnakangas <[email protected]> writes:
> Barring objections, I'll write a patch to relax the checking on
> default_text_search_config and temp_tablespaces to match search_path.
This seems like something that's going to come back again and again.
What do you think of changing things so that ALTER ROLE/DATABASE SET
*never* throw hard errors for bogus-seeming values?
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers