pgsql: Fix an ancient typo that prevented the detection of conflicting

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix an ancient typo that prevented the detection of conflicting
Date: 2010-08-02 01:25:02
Message-ID: 20100802012502.DEF1E7541D5@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix an ancient typo that prevented the detection of conflicting fields when
interval input "invalid" was specified together with other fields. Spotted
by Neil Conway with the help of a clang warning. Although this has been
wrong since the interval code was written more than 10 years ago, it doesn't
affect anything beyond which error message you get for a wrong input, so not
worth back-patching very far.

Tags:
----
REL9_0_STABLE

Modified Files:
--------------
pgsql/src/backend/utils/adt:
datetime.c (r1.212 -> r1.212.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/datetime.c?r1=1.212&r2=1.212.2.1)
pgsql/src/interfaces/ecpg/pgtypeslib:
interval.c (r1.42 -> r1.42.10.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/pgtypeslib/interval.c?r1=1.42&r2=1.42.10.1)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-08-02 02:29:39 pgsql: Tweak a couple of macros in the regex code to suppress compiler
Previous Message Tom Lane 2010-08-02 01:24:54 pgsql: Fix an ancient typo that prevented the detection of conflicting