| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Add support for coordinating record typmods among parallel worke |
| Date: | 2017-09-15 19:16:16 |
| Message-ID: | 20170915191616.zkaoqa34znssyfsj@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2017-09-15 15:07:14 -0400, Tom Lane wrote:
> It's moot as long as we're not reusing workers, anyway: nothing is
> going to touch any of the record-tupdesc data before process exit.
Right - I'm ok with the end-result, I was just a bit confused about the
justification, because neither before nor after the patch it's safe to
continue executing arbitrary things in the worker. Just unsafe in
different ways. Before you could reuse a typemod, now you can use a
dangling pointer.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-09-15 20:56:45 | Re: pgsql: Add support for coordinating record typmods among parallel worke |
| Previous Message | Tom Lane | 2017-09-15 19:07:14 | Re: pgsql: Add support for coordinating record typmods among parallel worke |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nico Williams | 2017-09-15 19:19:29 | Re: COMMIT TRIGGERs, take n, implemented with CONSTRAINT TRIGGERS |
| Previous Message | Tom Lane | 2017-09-15 19:07:14 | Re: pgsql: Add support for coordinating record typmods among parallel worke |