Re: sinval synchronization considered harmful

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Noah Misch" <noah(at)2ndquadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: sinval synchronization considered harmful
Date: 2011-07-27 16:39:11
Message-ID: 4E2FF8DF020000250003F80F@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> There turned out to be a little bit of further subtlety to this,
> but it seems to work. Patch attached.

Stylistic question: Why is stateP->hasMessages set to false in one
place and FALSE and TRUE in others? It seems like it would be less
confusing to be consistent.

A quick count of the usage of both forms in the PostgreSQL source
codes shows the lowercase is used about 10 times more often:

kgrittn(at)kgrittn-desktop:~/git/postgresql/kgrittn$ find -name '*.h'
-or -name '*.c' | egrep -v '/tmp_check/' | xargs cat | egrep -c
'\b(FALSE|TRUE)\b'
1670

kgrittn(at)kgrittn-desktop:~/git/postgresql/kgrittn$ find -name '*.h'
-or -name '*.c' | egrep -v '/tmp_check/' | xargs cat | egrep -c
'\b(false|true)\b'
17349

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-07-27 16:52:50 Re: sinval synchronization considered harmful
Previous Message Tom Lane 2011-07-27 16:34:35 Re: sinval synchronization considered harmful