Re: why cannot UNION both SELECT and SHOW? - Mailing list pgsql-general

From Jerry Sievers
Subject Re: why cannot UNION both SELECT and SHOW?
Date
Msg-id 87fwlkg79n.fsf@comcast.net
Whole thread Raw
In response to why cannot UNION both SELECT and SHOW?  (Konstantin Izmailov <pgfizm@gmail.com>)
List pgsql-general
Konstantin Izmailov <pgfizm@gmail.com> writes:

> Is it possible instead of executing following two statements:
> ? SHOW search_path; SELECT version();
> to execute just one statement returning both search_path and version?
>
> I'm using Postgres 9.0 and need the result either as two tuples or two fields...
>
> Could you suggest how to rewrite the two statements?



foo=# select current_setting('search_path'), version();
 current_setting |                                                     version
           

-----------------+-----------------------------------------------------------------------------------------------------------------
 "$user",public  | PostgreSQL 9.0.3 on x86_64-unknown-linux-gnu, compiled by GCC gcc (Ubuntu/Linaro 4.4.4-14ubuntu5)
4.4.5,64-bit 
(1 row)

>
> Thx
>

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 305.321.1144

pgsql-general by date:

Previous
From: "Reuven M. Lerner"
Date:
Subject: Re: Pending trigger events on ALTER TABLE in 8.3
Next
From: Rodrigo Gonzalez
Date:
Subject: Re: why cannot UNION both SELECT and SHOW?