pgsql: Mark application_name as GUC_REPORT so that the value will be

Поиск
Список
Период
Сортировка
От tgl@postgresql.org (Tom Lane)
Тема pgsql: Mark application_name as GUC_REPORT so that the value will be
Дата
Msg-id 20091202045410.95C2B753FB7@cvs.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
Mark application_name as GUC_REPORT so that the value will be reported back
to the client by the server.  This might seem pretty pointless but apparently
it will help pgbouncer, and perhaps other connection poolers.  Anyway it's
practically free to do so for the normal use-case where appname is only set
in the startup packet --- we're just adding a few more bytes to the initial
ParameterStatus response packet.  Per comments from Marko Kreen.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        libpq.sgml (r1.290 -> r1.291)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml?r1=1.290&r2=1.291)
        protocol.sgml (r1.75 -> r1.76)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/protocol.sgml?r1=1.75&r2=1.76)
    pgsql/src/backend/utils/misc:
        guc.c (r1.524 -> r1.525)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c?r1=1.524&r2=1.525)

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

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Instead of sending application_name as a SET command after the
Следующее
От: teodor@postgresql.org (Teodor Sigaev)
Дата:
Сообщение: pgsql: Preventing intersection of ranges during page split.