Re: [COMMITTERS] pgsql: Add new variable "server_version_num", which is almost the same

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Add new variable "server_version_num", which is almost the same
Date: 2006-09-02 16:39:16
Message-ID: 3907.1157215156@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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

Responses

Browse pgsql-committers by date

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

Browse pgsql-hackers by date

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