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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2010-10-25 17:46:13 | Re: BUG #5722: vacuum full does not update last_vacuum statistics |
Previous Message | Brendan Jurd | 2010-10-25 17:20:26 | Re: Segfault in 9.0 inlining SRF |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2010-10-25 17:42:35 | Re: ask for review of MERGE |
Previous Message | Kevin Grittner | 2010-10-25 17:20:27 | Re: Range Types, discrete and/or continuous |