| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marko Tiikkaja <pgmail(at)joh(dot)to>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7516: PL/Perl crash |
| Date: | 2012-09-06 23:03:05 |
| Message-ID: | 21328.1346972585@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> Another thing that seems a bit risky is that plperl_func_handler sets up
> current_call_data as a pointer to a mostly-zeroed struct and then does
> assorted things that could throw error. That would leave a dangling
> value of current_call_data ...
Meh, scratch that --- I missed that the caller of plperl_func_handler is
where there's a PG_TRY block that's responsible for restoring the old
value of current_call_data. It would still be interesting to nose
around and see what's in *current_call_data, as well as any of the
pointed-to data structures that exist.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2012-09-07 03:48:57 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |
| Previous Message | Tom Lane | 2012-09-06 22:26:20 | Re: BUG #7516: PL/Perl crash |