| From: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: On-demand running query plans using auto_explain and signals |
| Date: | 2015-09-29 10:52:11 |
| Message-ID: | CACACo5RuC_m1-U9ajtN2Hox8VZyagWAtRyQtbAvg0=CfYu0+Eg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 29, 2015 at 12:28 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
wrote:
> On 9/18/15 5:05 AM, Shulgin, Oleksandr wrote:
>
>>
>> So this has to be the responsibility of the reply sending backend in the
>> end: to create and release the DSM *at some point*.
>>
>
> What's wrong with just releasing it at the end of the statement? When the
> statement is done there's no point to reading it asynchronously anymore.
That was only one of the problems in signals-based design, and it has other
more significant problems. The current approach does exactly that:
allocate the segment before running the plan, release at the end of the
statement.
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-09-29 10:57:25 | Re: On-demand running query plans using auto_explain and signals |
| Previous Message | Kyotaro HORIGUCHI | 2015-09-29 10:27:22 | Re: PATCH: index-only scans with partial indexes |