Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER
Дата
Msg-id CAFj8pRCJS+gcJS2MH+L6H-P1j0i-njR+xBdFuxHT6N9NaCSirA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER  (Thomas Munro <thomas.munro@enterprisedb.com>)
Ответы Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER  (Thomas Munro <thomas.munro@enterprisedb.com>)
Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения
Hi

2017-08-16 6:58 GMT+02:00 Thomas Munro <thomas.munro@enterprisedb.com>:
On Thu, Jul 27, 2017 at 4:19 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> here is a patch - it is trivial

The feature makes sense, follows an existing example (PSQL_EDITOR),
and works nicely.

       is platform-dependent.  Use of the pager can be disabled by setting
       <envar>PAGER</envar> to empty, or by using pager-related options of

Maybe this should now say "... can be disabled by specifying an empty
string", since "... by setting PAGER to empty" isn't quite the full
story.

-      the <command>\pset</command> command.
+      the <command>\pset</command> command. These variables are examined
+      in the order listed; the first that is set is used.
      </para>
+

Stray blank line.

I am not sure if I see last issue well. Sending updated patch

Regards

Pavel
 

--
Thomas Munro
http://www.enterprisedb.com

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: [HACKERS] [PATCH] Remove unused argument in btree_xlog_split
Следующее
От: Andrey Borodin
Дата:
Сообщение: Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index