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

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


2017-09-05 18:06 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
Pavel Stehule <pavel.stehule@gmail.com> writes:
> [ psql-psql-pager-env-2.patch ]

Pushed, with some fooling with the documentation (notably,
re-alphabetizing relevant lists).

Grepping turned up an additional place that's examining the PAGER
environment variable, namely PQprint() in libpq/fe-print.c.  That's
not used by psql (or anything else in core PG) anymore; we're only
keeping it around for hypothetical external users of libpq.  I debated
whether to make it honor PSQL_PAGER.  I decided not to, since those
external users are by definition not psql ... but I added
a comment about that.

Thank you very much

Pavel
 

                        regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER
Следующее
От: Jacob Champion
Дата:
Сообщение: Re: [HACKERS] [PATCH] Assert that the correct locks are held whencalling PageGetLSN()