Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <peter@2ndquadrant.com>
Cc: Daniel Farina <daniel@heroku.com>, Robert Haas <robertmhaas@gmail.com>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2012-03-28T15:06:01Z
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 →

  1. Restructure SELECT INTO's parsetree representation into CreateTableAsStmt.

  2. Extend the parser location infrastructure to include a location field in

  3. Teach eval_const_expressions() to simplify an ArrayCoerceExpr to a constant

Attachments

Peter Geoghegan <peter@2ndquadrant.com> writes:
> Since you've already removed the intoClause chunk, I'm not sure how
> far underway the review effort is - would you like me to produce a new
> revision, or is that unnecessary?

I've whacked it around to the point that that wouldn't be too helpful
as far as the code goes.  (Just for transparency I'll attach what I've
currently got, which mostly consists of getting rid of the static state
and cleaning up the scanner interface a bit.  I've not yet touched the
jumble-producing code, but I think it needs work too.)  However, if
you've got or can produce the appropriate documentation updates, that
would save me some time.

			regards, tom lane