Re: why cannot UNION both SELECT and SHOW?
От
Jerry Sievers
Тема
Re: why cannot UNION both SELECT and SHOW?
Дата
Msg-id
87fwlkg79n.fsf@comcast.net
Ответ на
why cannot UNION both SELECT and SHOW? (Konstantin Izmailov)
Список
Дерево обсуждения
why cannot UNION both SELECT and SHOW? Konstantin Izmailov <pgfizm@gmail.com>
Re: why cannot UNION both SELECT and SHOW? Adrian Klaver <adrian.klaver@gmail.com>
Re: why cannot UNION both SELECT and SHOW? Rodrigo Gonzalez <rjgonzale@estrads.com.ar>
Re: why cannot UNION both SELECT and SHOW? Jerry Sievers <gsievers19@comcast.net>
Konstantin Izmailov 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 по дате отправления