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

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>

To: Peter Geoghegan <peter@2ndquadrant.com>

Cc: Peter Eisentraut <peter_e@gmx.net>, Greg Stark <stark@mit.edu>, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, PG Hackers <pgsql-hackers@postgresql.org>

Date: 2012-03-20T17:21:57Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Restructure SELECT INTO's parsetree representation into CreateTableAsStmt.
- 9dbf2b7d75de 9.2.0 cited
Extend the parser location infrastructure to include a location field in
- a2794623d292 8.4.0 cited
Teach eval_const_expressions() to simplify an ArrayCoerceExpr to a constant
- 6734182c169a 8.4.0 cited

On Mon, Mar 19, 2012 at 08:48:07PM +0000, Peter Geoghegan wrote:
> On 19 March 2012 19:55, Peter Eisentraut <peter_e@gmx.net> wrote:
> > If someone wanted to bite the bullet and do the work, I think we could
> > move to a Perl/TAP-based test suite (not pgTAP, but Perl and some fairly
> > standard Test::* modules) and reduce that useless reformatting work and
> > test more interesting things.  Just a thought ...
> 
> I think that that is a good idea. However, I am not a Perl hacker,
> though this is the second time that that has left me at a disadvantage
> when working on Postgres, so I think it's probably time to learn a
> certain amount.

My blog entry on this topic might be helpful:

	http://momjian.us/main/blogs/pgblog/2008.html#October_4_2008_2

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +