| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Core dump with nested CREATE TEMP TABLE |
| Date: | 2015-09-02 19:17:15 |
| Message-ID: | 20150902191715.GU2912@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier wrote:
> I haven't written yet a test case but I think that we could reproduce
> that simply by having a relation referenced in the exception block of
> a first function, calling a second function that itself raises an
> exception, causing the referencing error.
Hm, so function 2 is called in the exception block of function 1?
Are you going to produce the test case for this? Jim?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-09-02 19:24:33 | Re: Memory prefetching while sequentially fetching from SortTuple array, tuplestore |
| Previous Message | Julien Rouhaud | 2015-09-02 19:12:41 | Re: Allow a per-tablespace effective_io_concurrency setting |