From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Васильев Дмитрий <d(dot)vasilyev(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Performance degradation in commit ac1d794 |
Date: | 2016-03-17 13:40:08 |
Message-ID: | CA+TgmoZc4_pLg_xo_2O5vvsKH1uED0RK7heMuMMyw0BCLshFpw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 17, 2016 at 9:01 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I'll look at 0005 next, but thought I would send these comments along first.
0005: This is obviously very much WIP, but I think the overall
direction of it is good.
0006: Same.
I think you should use PGINVALID_SOCKET rather than -1 in various
places in various patches in this series, especially if you are going
to try to merge the Windows code path.
I wonder if CreateEventSet should accept a MemoryContext argument. It
seems like callers will usually want TopMemoryContext, and just being
able to pass that might be more convenient than having to switch back
and forth in the calling code.
I wonder if there's a way to refactor this code to avoid having so
much cut-and-paste duplication.
When iterating over the returned events, maybe check whether events is
0 at the top of the loop and skip it forthwith if so.
That's all I've got for now.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-03-17 13:40:50 | Re: Pushdown target list below gather node (WAS Re: WIP: Upper planner pathification) |
Previous Message | Tom Lane | 2016-03-17 13:35:50 | Re: typmod is always -1 |