Re: Slowness of extended protocol

From: Shay Rojansky <roji(at)roji(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Greg Stark <stark(at)mit(dot)edu>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Slowness of extended protocol
Date: 2016-08-06 00:07:37
Message-ID: CADT4RqBsynKtSSRbPZLGpvXJKO4W_Ae2obn3rRkrQqZy7RAJWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> > I really don't get what's problematic with posting a message on a mailing
> > list about a potential performance issue, to try to get people's
> reactions,
> > without diving into profiling right away. I'm not a PostgreSQL developer,
> > have other urgent things to do and don't even spend most of my
> programming
> > time in C.
>
> There's absolutely nothing wrong with that. I find your questions
> helpful and interesting and I hope you will keep asking them. I think
> that they are a valuable contribution to the discussion on this list.
>

Thanks for the positive feedback Robert.

I'm glad reducing the overhead of out-of-line parameters seems like an
important goal. FWIW, if as Vladimir seems to suggest, it's possible to
bring down the overhead of the v3 extended protocol to somewhere near the
simple protocol, that would obviously be a better solution - it would mean
things work faster here and now, rather than waiting for the v4 protocol. I
have no idea if that's possible though, I'll see if I can spend some time
on understand where the slowdown comes from.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2016-08-06 00:21:49 Re: Heap WARM Tuples - Design Draft
Previous Message Bruce Momjian 2016-08-06 00:07:18 Re: Heap WARM Tuples - Design Draft