I'd be less unhappy with this patch if the variable were not marked
GUC_REPORT.  That is what gives it nontrivial cost: it's adding a couple
dozen bytes to every connection startup exchange, for data that's 100%
redundant with data already being transmitted.

The arguments that were made in favor of this patch cited its possible
use in SQL scripts, but there is no need for the variable to be marked
GUC_REPORT for that usage.

			regards, tom lane

In response to

• Re: [COMMITTERS] pgsql: Add new variable "server_version_num", which is almost the same at 2006-09-02 14:30:06 from Tom Lane

Responses

• Re: [COMMITTERS] pgsql: Add new variable at 2006-09-02 16:41:22 from Bruce Momjian
• Re: [COMMITTERS] pgsql: Add new variable at 2006-09-02 17:08:19 from Bruce Momjian

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 2006-09-02 16:40:34
	Subject: Re: Getting a move on for 8.2 beta
Previous:	From: Hannu Krosing	Date: 2006-09-02 16:30:16
	Subject: Re: [COMMITTERS] pgsql: Allow PL/python to return

pgsql-committers by date

Next:	From: Bruce Momjian	Date: 2006-09-02 16:41:22
	Subject: Re: [COMMITTERS] pgsql: Add new variable
Previous:	From: Hannu Krosing	Date: 2006-09-02 16:30:16
	Subject: Re: [COMMITTERS] pgsql: Allow PL/python to return