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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Selena Deckelmann <selena(at)chesnok(dot)com>
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:00:59
Message-ID: 641.1349121659@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2012-10-01 20:04:54 Re: setting per-database/role parameters checks them against wrong context
Previous Message Selena Deckelmann 2012-10-01 19:37:19 Re: setting per-database/role parameters checks them against wrong context