On Jul 27, 2012, at 8:47 AM, Tom Lane wrote:
> Craig Ringer writes:
>> OK, it's certainly leaking, but not in the same drastic way I was able
>> to reproduce manually a couple of times earlier. Self-contained test
>> case attached.
>
> Using HEAD with stock parameters, I don't see any signifi
On 07/27/2012 07:52 PM, luben karavelov wrote:
It's good that the bug is not in HEAD. I was testing on 9.1.4.
So was I, and while I thought I'd reproduced it I now suspect I was just
seeing shared_buffers touching.
Are you able to produce a self-contained SQL test that demonstrates the
leak?
On 07/27/2012 07:52 AM, fabio.lun...@gmail.com wrote:
The following bug has been logged on the website:
Bug reference: 6768
Logged by: Fábio Hentz Lunkes
Email address: fabio.lun...@gmail.com
PostgreSQL version: 9.1.0
Operating system: Windows 7
Description:
Hellow.
My test
This problem has been resolved; following a couple of suggestions from Tom
Lane, it became apparent that the cause was due to the xlc compiler. This mail
summarizes the steps and findings, in the hope that it might be useful to
someone else.
My server environment is AIXv7.1 running on POWER7,
The following bug has been logged on the website:
Bug reference: 6774
Logged by: Boris Folgmann
Email address: bo...@folgmann.de
PostgreSQL version: 8.4.12
Operating system: CentOS 6.3
Description:
This is an really interesting one!
I've trimmed down the problem so yo
On Fri, Jul 27, 2012 at 02:56:18PM +, bo...@folgmann.de wrote:
> This is an really interesting one!
> I've trimmed down the problem so you can simply reproduce it by copy &
> paste:
> The only difference of the two functions is that the first one uses a
> variable with the same name of a column
