Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Mark application_name as GUC_REPORT so that the value will be - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Mark application_name as GUC_REPORT so that the value will be
Date
Msg-id 20091202045410.95C2B753FB7@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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 by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Instead of sending application_name as a SET command after the
Next
From: teodor@postgresql.org (Teodor Sigaev)
Date:
Subject: pgsql: Preventing intersection of ranges during page split.