| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Fix memory leak in plpgsql's CALL processing. |
| Date: | 2020-12-28 15:11:40 |
| Message-ID: | 1598242.1609168300@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> This change has broken the following test case (reduced from actual
> production code):
Thanks for the report. What I see here is
ERROR: unsupported target type: 2139062143
so it looks like a memory clobber --- probably some data structure is
being built in the wrong memory context. Will look closer shortly.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-12-28 15:34:00 | Re: pgsql: Add pg_alterckey utility to change the cluster key |
| Previous Message | Fabien COELHO | 2020-12-28 14:09:11 | Re: pgsql: Add pg_alterckey utility to change the cluster key |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-12-28 15:34:00 | Re: pgsql: Add pg_alterckey utility to change the cluster key |
| Previous Message | Masahiko Sawada | 2020-12-28 14:24:10 | Re: Transactions involving multiple postgres foreign servers, take 2 |