[HACKERS] [COMMITTERS] 'postgres95/src/backend/tcop variable.c' (fwd) - Mailing list pgsql-hackers

From Bruce Momjian
Subject [HACKERS] [COMMITTERS] 'postgres95/src/backend/tcop variable.c' (fwd)
Date
Msg-id 50d946acc7d2df1a0909194c5978540d
Whole thread Raw
List pgsql-hackers
Forwarded message:
> From owner-committers@hub.org Tue Jun  3 02:31:05 1997
> Date: Tue, 3 Jun 1997 02:29:37 -0400 (EDT)
> From: "Vadim B. Mikheev - CVS" <vadim@wakko.chicks.net>
> Message-Id: <199706030629.CAA00403@hub.org>
> To: committers@postgreSQL.org
> Subject: [COMMITTERS] 'postgres95/src/backend/tcop variable.c'
> Sender: owner-cvs-commit@hub.org
> Precedence: bulk
>
> Update of /usr/local/cvsroot/postgres95/src/backend/tcop
> In directory hub.org:/home/users/v/vadim/postgres95/src/backend/tcop
>
> Modified Files:
>     variable.c
> Log Message:
> SET geqo TO 'on' restores _use_geqo_rels_ to GEQO_RELS, not
> to last specified with 'on' #.
> What is better ?

I think "SET geqo TO ON" should set it back to GEQO_RELS, not to the
last SET geqo TO ON=# value.  The manual page clearly says that, and I
think it is clearer.

- --
Bruce Momjian
maillist@candle.pha.pa.us

------------------------------

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: [HACKERS] Path and Polygon types
Next
From: Anthony Heading
Date:
Subject: Re: [HACKERS] 6.1 issues resolved