Skip site navigation (1) Skip section navigation (2)

Re: Segfault in 9.0 inlining SRF

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Brendan Jurd <direvus(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Segfault in 9.0 inlining SRF
Date: 2010-10-25 17:28:36
Message-ID: 16881.1288027716@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Brendan Jurd <direvus(at)gmail(dot)com> writes:
> This whole business of passing around global pointers while switching
> memory contexts seems like an optimal breeding-ground for bugs.

Yeah.  If it were to get significantly more complicated than this,
the best solution IMO would be to give up on trying to use a temporary
memory context during function inlining, and just accept that whatever
memory we chew up there is going to be leaked for the duration of
planning.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Greg StarkDate: 2010-10-25 17:42:35
Subject: Re: ask for review of MERGE
Previous:From: Kevin GrittnerDate: 2010-10-25 17:20:27
Subject: Re: Range Types, discrete and/or continuous

pgsql-bugs by date

Next:From: Greg StarkDate: 2010-10-25 17:46:13
Subject: Re: BUG #5722: vacuum full does not update last_vacuum statistics
Previous:From: Brendan JurdDate: 2010-10-25 17:20:26
Subject: Re: Segfault in 9.0 inlining SRF

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group