Horton
Menu

Re: proposal - assign result of query to psql variable

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Phil Sorber <phil@omniti.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, Shigeru HANADA <shigeru.hanada@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Erik Rijkers <er@xs4all.nl>, David Fetter <david@fetter.org>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2012-10-25T14:24:14Z
Lists: pgsql-hackers 
I gave this a look.  I think it needs to be revised by somebody with a
better understanding of scanner (flex) than me, but I didn't like the
changes in psqlscan.l at all; the new <xvl> pattern is too unlike the
rest of the surrounding patterns, and furthermore it has been placed
within the block that says it mirrors the backend scanner, when it
obviously has no equivalent there.

I assume there's a better way to do this.  Hints would be appreciated.

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

Commits

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

  1. Fix oversight in new code for printing rangetable aliases.