2009/6/23 Tom Lane <t...@sss.pgh.pa.us>: > Brendan Jurd <dire...@gmail.com> writes: >> I should be able to get the same results by snipping an extra >> strspace_len() characters in the new code path in >> from_char_parse_int_len(). This ought to be a one-line fix that >> doesn't clobber the good parts of my work so far. I'll run some tests >> and then post a patch within the hour. Does that work for you? > > +1 >
[cross-posting to -hackers] Here's a one-line patch to fix a regression in the new from_char code I introduced into 8.4. Versions <= 8.3 skipped over any whitespace immediately preceding any integer field, and this behaviour was lost in HEAD when my from_char patch was committed back in September '08 [1]. Fortunately, since the code has been refactored, this now only needs to be repaired in one place =) With thanks to Jeremy Ford for sending in his bug report, and an abject mea culpa. Cheers, BJ [1] http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6f09ab2c24491a217f8b88012aababf3b723b902
from_char-skip-whitespace.diff
Description: Binary data
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
