Postgres Pro
Downloads
Home   >   mailing lists

Re: Memory leak in deferrable index constraints - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Memory leak in deferrable index constraints
Date
Msg-id 25059.1264953781@sss.pgh.pa.us
Whole thread Raw
In response to Memory leak in deferrable index constraints  (Dean Rasheed <dean.a.rasheed@googlemail.com>)
Responses Re: Memory leak in deferrable index constraints  (Dean Rasheed <dean.a.rasheed@googlemail.com>)
List pgsql-hackers
Tree view 
Dean Rasheed <dean.a.rasheed@googlemail.com> writes:
> Oops, my fault. The list returned by ExecInsertIndexTuples() needs to be
> freed otherwise lots of lists (one per row) will build up and not be freed
> until the end of the query. This actually accounts for even more memory
> than the after-trigger event queue. Patch attached.

It seems a bit unlikely that this would be the largest memory leak in
that area.  Can you show a test case that demonstrates this is worth
worrying about?
        regards, tom lane

pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Memory leak in deferrable index constraints
Next
From: Tom Lane
Date:
Subject: Re: ordered aggregates using WITHIN GROUP (was Re: can somebody execute this query on Oracle 11.2g and send result?)