pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Mark Rofail <markm.rofail@gmail.com>
Cc: David Steele <david@pgmasters.net>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Erik Rijkers <er@xs4all.nl>
Cc: Hans-Jürgen Schönig <hs@cybertec.at>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Date: Tue, 10 Apr 2018 11:17:43 -0300
Message-ID: <20180410141743.aphekyopkbre3avp@alvherre.pgsql> (raw)
In-Reply-To: <CAJvoCutzj34v_xfVtpQXNMEyYd8n13LSg2WCzHWhTqQhnB4ZzA@mail.gmail.com>

Mark Rofail wrote:
> On Tue, Apr 10, 2018 at 3:59 PM, Alvaro Herrera <alvherre@alvh.no-ip.org>
> wrote:
> >
> > documentation to it and a few extensive tests to ensure it works well);
> 
> I think the existing regression tests verify that the patch works as
> expectations, correct?

I meant for the GIN operator. (Remember, these are two patches, and each
of them needs its own tests.)

> We need more *exhaustive* tests to test performance, not functionality.

True.  So my impression from the numbers you posted last time is that
you need to run each measurement case several times, and provide
averages/ stddevs/etc for the resulting numbers, and see about outliers
(maybe throw them away, or maybe they indicate some problem in the test
or in the code); then we can make an informed decision about whether the
variations between the several different scenarios are real improvements
(or pessimizations) or just measurement noise.

In particular: it seemed to me that you decided to throw away the idea
of the new GIN operator without sufficient evidence that it was
unnecessary.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (200+ messages)  latest in thread

Message-ID: <20180410141743.aphekyopkbre3avp@alvherre.pgsql>
Permalink:  ../20180410141743.aphekyopkbre3avp@alvherre.pgsql/
Also on:    postgresql.org/message-id/20180410141743.aphekyopkbre3avp@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@alvh.no-ip.org, markm.rofail@gmail.com, david@pgmasters.net, andreas@proxel.se, aekorotkov@gmail.com, er@xs4all.nl, hs@cybertec.at, robertmhaas@gmail.com, sfrost@snowman.net, tgl@sss.pgh.pa.us
  Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
  In-Reply-To: <20180410141743.aphekyopkbre3avp@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox