Re: Record comparison compiler warning

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Record comparison compiler warning
Date: 2013-11-02 15:18:31
Message-ID: 9700.1383405511@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Stefan Kaltenbrunner wrote:
>> http://www.postgresql.org/message-id/raw/1381949353(dot)78943(dot)YahooMailNeo(at)web162902(dot)mail(dot)bf1(dot)yahoo(dot)com

> I would blame Bruce's MUA, or surrounding configuration, for this
> problem. It looks fine in mine, and as far as I can see, Kevin's
> message correctly declares the email to be in Latin-1 quoted-printable
> encoding, which declares A0 to mean non-breaking space.

I agree with Bruce: this patch is broken. A0 may be a non-breaking space,
but the fact remains that it isn't a space, and since we're talking about
a diff, the whitespace needs to be the same as what it is in the original
file. (I believe that some of those whitespace runs involve tabs not just
spaces, making the diff even more wrong.)

Admittedly, if you're just eyeballing it, it might look fine. But try
feeding it to "patch" and you'll find out it ain't.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sawada Masahiko 2013-11-02 15:25:33 Re: Patch for fail-back without fresh backup
Previous Message Tom Lane 2013-11-02 15:06:07 Re: Handle LIMIT/OFFSET before select clause (was: Feature request: optimizer improvement)