Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)

From: Noah Misch <noah(at)leadboat(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
Date: 2012-03-20 04:29:49
Message-ID: 20120320042949.GD8199@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 19, 2012 at 09:49:32PM +0200, Peter Eisentraut wrote:
> On m??n, 2012-03-19 at 02:35 +0000, Peter Geoghegan wrote:
> > I see your point of view. I suppose I can privately hold onto the test
> > suite, since it might prove useful again.
>
> I would still like to have those tests checked in, but not run by
> default, in case someone wants to hack on this particular feature again.

Agreed. Also, patch review becomes materially smoother when the author
includes comprehensive tests. When a usage I wish to verify already appears
in the submitted tests, that saves time. I respect the desire to keep regular
"make check" lean, but not if it means comprehensive tests get written to be
buried in the mailing list archives or never submitted at all.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Farina 2012-03-20 04:33:40 Re: Incorrect assumptions with low LIMITs
Previous Message Erik Rijkers 2012-03-20 04:13:07 Re: patch for parallel pg_dump