Did this ever get turned into a formal bug report with a number?
Tim.
On Thu, Jan 14, 2010 at 07:39:09PM -0500, Andrew Dunstan wrote:
Tim Bunce just showed me the following oddity:
andrew=# SET SESSION plperl.use_strict = on;
SET
andrew=# SHOW plperl.use_strict;
Tim Bunce wrote:
Did this ever get turned into a formal bug report with a number?
No, and nobody seemed to care much about the poroblem :-( Maybe I will
get a chance to do something about it during the next few weeks,
although I am currently busier than a one legged man in a
On Jan 19, 2010, at 9:26 PM, Andrew Dunstan wrote:
The first thing I think we need to do is move the GUC processing code out of
_PG_init() and into plperl_init_interp(), protected by a flag to make sure
it's only called successfully once. I'm trying to work out a neat way to put
the value
Andrew Dunstan wrote:
Tim Bunce just showed me the following oddity:
andrew=# SET SESSION plperl.use_strict = on;
SET
andrew=# SHOW plperl.use_strict;
plperl.use_strict
---
on
(1 row)
andrew=# DO $$ elog(ERROR,error) $$ language plperl;
ERROR:
Tim Bunce just showed me the following oddity:
andrew=# SET SESSION plperl.use_strict = on;
SET
andrew=# SHOW plperl.use_strict;
plperl.use_strict
---
on
(1 row)
andrew=# DO $$ elog(ERROR,error) $$ language plperl;
ERROR: error at line 1.
