Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2013-01-25 Thread Bruce Momjian
On Fri, Jan 25, 2013 at 03:35:59PM -0500, Tom Lane wrote: > Bruce Momjian writes: > >> diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c > >> index 6b202e0..0677059 100644 > >> --- a/src/backend/utils/misc/guc.c > >> +++ b/src/backend/utils/misc/guc.c > >> @@ -5150,7 +5150,7

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2013-01-25 Thread Tom Lane
Bruce Momjian writes: >> diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c >> index 6b202e0..0677059 100644 >> --- a/src/backend/utils/misc/guc.c >> +++ b/src/backend/utils/misc/guc.c >> @@ -5150,7 +5150,7 @@ set_config_option(const char *name, const char *value, >> elevel =

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2013-01-25 Thread Bruce Momjian
On Sat, Oct 6, 2012 at 02:20:53PM -0700, Selena Deckelmann wrote: > On Mon, Oct 1, 2012 at 2:28 PM, Selena Deckelmann wrote: > > On Mon, Oct 1, 2012 at 1:37 PM, Selena Deckelmann > > wrote: > >> On Mon, Oct 1, 2012 at 1:00 PM, Tom Lane wrote: > >>> Selena Deckelmann writes: > The check_t

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2012-10-06 Thread Selena Deckelmann
On Mon, Oct 1, 2012 at 2:28 PM, Selena Deckelmann wrote: > On Mon, Oct 1, 2012 at 1:37 PM, Selena Deckelmann wrote: >> On Mon, Oct 1, 2012 at 1:00 PM, Tom Lane wrote: >>> Selena Deckelmann writes: The check_temp_buffers() problem seems like a regression and blocks us from upgrading to

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2012-10-01 Thread Selena Deckelmann
On Mon, Oct 1, 2012 at 1:37 PM, Selena Deckelmann wrote: > On Mon, Oct 1, 2012 at 1:00 PM, Tom Lane wrote: >> Selena Deckelmann writes: >>> The check_temp_buffers() problem seems like a regression and blocks us >>> from upgrading to 9.2. The use case are functions that set >>> temp_buffers and o

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2012-10-01 Thread Selena Deckelmann
On Mon, Oct 1, 2012 at 1:00 PM, Tom Lane wrote: > Selena Deckelmann writes: >> The check_temp_buffers() problem seems like a regression and blocks us >> from upgrading to 9.2. The use case are functions that set >> temp_buffers and occasionally are called in a series from a parent >> session. Th

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2012-10-01 Thread Josh Berkus
> Uh ... how is that a regression? AFAIK it's been that way right along. No, it hasn't. I currently have an application whose functions, each of which sets temp_buffers, works fine under 9.0 and ERRORs out under 9.2. It's blocking an upgrade. This is new. -- Josh Berkus PostgreSQL Experts I

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2012-10-01 Thread Tom Lane
Selena Deckelmann writes: > The check_temp_buffers() problem seems like a regression and blocks us > from upgrading to 9.2. The use case are functions that set > temp_buffers and occasionally are called in a series from a parent > session. The work around is... a lot of work. Uh ... how is that

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2012-10-01 Thread Selena Deckelmann
On Fri, Sep 28, 2012 at 7:10 AM, Tom Lane wrote: > Peter Eisentraut writes: >> Example: >> create temporary table foo (a int); >> insert into foo values (1); >> alter role peter set temp_buffers = 120; >> ERROR: 22023: invalid value for parameter "temp_buffers": 120 >> DETAIL: "temp_buffers" ca

Re: [HACKERS] setting per-database/role parameters checks them against wrong context

2012-09-28 Thread Tom Lane
Peter Eisentraut writes: > Example: > create temporary table foo (a int); > insert into foo values (1); > alter role peter set temp_buffers = 120; > ERROR: 22023: invalid value for parameter "temp_buffers": 120 > DETAIL: "temp_buffers" cannot be changed after any temporary tables > have been acc

[HACKERS] setting per-database/role parameters checks them against wrong context

2012-09-27 Thread Peter Eisentraut
Example: create temporary table foo (a int); insert into foo values (1); alter role peter set temp_buffers = 120; ERROR: 22023: invalid value for parameter "temp_buffers": 120 DETAIL: "temp_buffers" cannot be changed after any temporary tables have been accessed in the session. Another example: