Skip site navigation (1) Skip section navigation (2)

pgsql: Remove some of the most blatant brain-fade in the recent guc

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove some of the most blatant brain-fade in the recent guc
Date: 2007-04-22 03:52:40
Message-ID: 20070422035240.878119FB33C@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Log Message:
-----------
Remove some of the most blatant brain-fade in the recent guc patch
(it's so nice to have a buildfarm member that actively rejects naked
uses of strcasecmp).  This coding is still pretty awful, though, since
it's going to be O(N^2) in the number of guc variables.  May I direct
your attention to bsearch?

Modified Files:
--------------
    pgsql/src/backend/utils/misc:
        guc.c (r1.387 -> r1.388)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.387&r2=1.388)

Responses

pgsql-hackers by date

Next:From: rancpine cuiDate: 2007-04-22 07:04:10
Subject: what's the difference among "session"&"backend"&"process"?
Previous:From: Tom LaneDate: 2007-04-22 02:34:57
Subject: Re: 27 second plan times

pgsql-committers by date

Next:From: Bruce MomjianDate: 2007-04-22 13:26:20
Subject: Re: [COMMITTERS] pgsql: Some further performance tweaks for planning large inheritance
Previous:From: Tom LaneDate: 2007-04-21 21:01:46
Subject: pgsql: Some further performance tweaks for planning large inheritance

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group