| From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Stephen Denne" <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: 8.3rc1 Out of memory when performing update |
| Date: | 2008-01-28 08:18:08 |
| Message-ID: | 1d4e0c10801280018x17103cc8o7ead9fdc75d69470@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Jan 25, 2008 5:50 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Lunnon | 2008-01-28 11:41:41 | Performance issues migrating from 743 to 826 |
| Previous Message | Tory M Blue | 2008-01-28 06:09:12 | Re: Postgres 8.2 memory weirdness |