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

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

From: Selena Deckelmann <selena(at)chesnok(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: setting per-database/role parameters checks them against wrong context
Date: 2012-10-01 20:37:11
Message-ID: CAN1EF+yuq7Dr4Dwp59mS_W=-wgJGnvVf4PAYjc0QK_9NdgzcHg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Oct 1, 2012 at 1:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Selena Deckelmann <selena(at)chesnok(dot)com> 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 a regression?  AFAIK it's been that way right along.

We're running 9.0 - looks like it changed in 9.1, last revision to the
relevant line was 6/2011. The group decided not to upgrade to 9.1 last
year, but was going to just go directly to 9.2 in the next few weeks.

-selena

-- 
http://chesnok.com


In response to

Responses

pgsql-hackers by date

Next:From: sccDate: 2012-10-01 20:50:29
Subject: Re: moving system catalogs to another tablespace
Previous:From: Jaime CasanovaDate: 2012-10-01 20:35:57
Subject: Re: moving system catalogs to another tablespace

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