Excerpts from Pavel Stehule's message of mié sep 07 14:23:43 -0300 2011: > Hello > > Andy Colson found a bug in GUC implementation. > > When we have a custom SUSET variable, like plpgsql.variable_conflikt, > then setting this variable before plpgsql initalisation raises a > exception, but it raise a exception when some plpgsql function is > created. Try to execute a attached script - a set statement is ok, but > CREATE FUNCTION fails.
Another thing we detected some days ago is that a custom variable in a module not loaded by postmaster, does not seem to get reported appropriately when an invalid value is set on postgresql.conf and reloaded: backends report problems with DEBUG3, only postmaster uses LOG, but since postmaster isn't loading the module, nothing happens. (Maybe this is our bug but it doesn't seem like it.) -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers