From: Guillaume Smet <guillaume.smet@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Denne <Stephen.Denne@datamail.co.nz>
Cc: pgsql-performance@postgresql.org
Subject: Re: 8.3rc1 Out of memory when performing update
Date: Mon, 28 Jan 2008 09:18:08 +0100
Message-ID: <1d4e0c10801280018x17103cc8o7ead9fdc75d69470@mail.gmail.com> (raw)
In-Reply-To: <22975.1201236625@sss.pgh.pa.us>
References: <F0238EBA67824444BC1CB4700960CB480482B525@dmpeints002.isotach.com>
<21675.1201228274@sss.pgh.pa.us>
<F0238EBA67824444BC1CB4700960CB480482B5B7@dmpeints002.isotach.com>
<22975.1201236625@sss.pgh.pa.us>
On Jan 25, 2008 5:50 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Hmm. I think what that really means is you haven't got to the part of
> the query where the leak is :-(. In my attempt to reproduce this
> I found that 8.3 has introduced a memory leak into the RI trigger
> support, such that even if an UPDATE doesn't change the FK columns
> it's still likely to leak a few dozen bytes per updated row.
>
> Please see if the attached patch makes it better for you.
Just FYI, somebody on #postgresql had the exact same problem of
memleaks during update yesterday and your patch fixed it for him too.
--
Guillaume
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: guillaume.smet@gmail.com, tgl@sss.pgh.pa.us, Stephen.Denne@datamail.co.nz
Subject: Re: 8.3rc1 Out of memory when performing update
In-Reply-To: <1d4e0c10801280018x17103cc8o7ead9fdc75d69470@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox