Horton
Menu

Re: proposal - assign result of query to psql variable

Erik Rijkers <er@xs4all.nl>

View thread
From: "Erik Rijkers" <er@xs4all.nl>
To: "Pavel Stehule" <pavel.stehule@gmail.com>
Cc: "Shigeru HANADA" <shigeru.hanada@gmail.com>, "David Fetter" <david@fetter.org>, "Tom Lane" <tgl@sss.pgh.pa.us>, "PostgreSQL Hackers" <pgsql-hackers@postgresql.org>
Date: 2012-10-13T22:11:14Z
Lists: pgsql-hackers 
On Sat, October 13, 2012 19:26, Pavel Stehule wrote:
> 2012/10/13 Shigeru HANADA <shigeru.hanada@gmail.com>:
>> After you determine whether it's ok or unnecessary, I'll mark this patch as
>> "Ready for committer".
>>
>

I found this behaviour which I think must count as a bug.
\gset doesn't allow more \\-separated lines behind it:

Only the last of these commands is problematic, and giving the syntax error

$ psql
psql (9.3devel-psql_var-20121012_2345-8b728e5c6e0ce6b6d6f54b92b390f14aa1aca6db)
Type "help" for help.

testdb=# select 1,2 \gset x,y
testdb=# \echo :x
1
testdb=# \echo :y
2
testdb=# \echo :x \\ \echo :y
1
2
testdb=# select 1,2 \gset x,y \\ \echo :x
\gset: syntax error
testdb=#

It'd be nice if it could be made to work

Thanks

Erik Rijkers

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.