Skip site navigation (1) Skip section navigation (2)

GUC failure on exception

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: GUC failure on exception
Date: 2010-01-15 00:39:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tim Bunce just showed me the following oddity:

    andrew=# SET SESSION plperl.use_strict = on;
    andrew=# SHOW plperl.use_strict;
    (1 row)

    andrew=# DO $$ elog(ERROR,"error") $$ language plperl;
    ERROR:  error at line 1.
    CONTEXT:  PL/Perl anonymous code block
    andrew=# SHOW plperl.use_strict;
    (1 row)

Somehow we have lost the setting, because the first use of plperl, which 
called the plperl init code, failed.

It appears that whatever rolls it back forgets to put the GUC setting 
back as it was, and now it's lost, which is pretty darn ugly. And you 
can now run code which fails the 'strict' tests.

If anyone has a quick idea about how to fix that would be nice. 
Otherwise I'll try to delve into it as time permits.




pgsql-hackers by date

Next:From: KaiGai KoheiDate: 2010-01-15 00:56:10
Subject: Re: [PATCH] remove redundant ownership checks
Previous:From: Tim BunceDate: 2010-01-15 00:35:06
Subject: Add on_trusted_init and on_untrusted_init to plperl [PATCH]

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group