Re: proposal - assign result of query to psql variable - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: proposal - assign result of query to psql variable
Date
Msg-id 20121025142414.GA6442@alvh.no-ip.org
Whole thread Raw
In response to Re: proposal - assign result of query to psql variable  (Phil Sorber <phil@omniti.com>)
Responses Re: proposal - assign result of query to psql variable  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: autovacuum truncate exclusive lock round two
Next
From: Tom Lane
Date:
Subject: Re: proposal - assign result of query to psql variable