Re: Performance degradation in commit ac1d794

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Васильев Дмитрий <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-01-14 16:30:03
Message-ID: 80E22476-FE7F-43FA-846B-BF736550CEA2@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On January 14, 2016 5:16:59 PM GMT+01:00, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>Yeah. Although I think for now it would be fine to just error out if
>somebody tries to add a socket and there already is one. Then we
>could lift that limitation in a later commit. Of course if Andres
>wants to do the whole thing now I'm not going to get in the way, but
>since that will require Windows tinkering and so on it may be more
>than he wants to dive into.

Yea, I don't want to do anything really large at the moment. My primary interest is fixing the major performance regression.

Andres

---
Please excuse brevity and formatting - I am writing this on my mobile phone.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-01-14 16:31:03 Re: Performance degradation in commit ac1d794
Previous Message Andrew Dunstan 2016-01-14 16:25:20 Re: pgindent-polluted commits