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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Mark application_name as GUC_REPORT so that the value will be
Date: 2009-12-02 04:54:10
Message-ID: 20091202045410.95C2B753FB7@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Teodor Sigaev 2009-12-02 13:13:24 pgsql: Preventing intersection of ranges during page split.
Previous Message Tom Lane 2009-12-02 04:38:35 pgsql: Instead of sending application_name as a SET command after the