custom variables and PGC_SUSET issue

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: custom variables and PGC_SUSET issue
Date: 2011-09-07 17:23:43
Message-ID: CAFj8pRCD4E1tB_2EU10fj6hmkosZRxZZAnKdugK6mcZ7dg7EgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

repeated setting this GUC raise a strange message

postgres=# \i script.sql
SET
before create function
psql:script.sql:13: ERROR: 42501: permission denied to set parameter
"plpgsql.variable_conflict"
LOCATION: set_config_option, guc.c:5208
after function
postgres=# \i script.sql
SET
before create function
psql:script.sql:13: ERROR: XX000: attempt to redefine parameter
"plpgsql.variable_conflict"
LOCATION: define_custom_variable, guc.c:6333
after function

Regards

Pavel Stehule

Attachment Content-Type Size
script.sql text/x-sql 251 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-09-07 17:25:42 Re: typo
Previous Message Tom Lane 2011-09-07 17:05:09 Re: [v9.2] Fix Leaky View Problem