| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | 高增琦 <pgf00a(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Try to fix endless loop in ecpg with informix mode |
| Date: | 2017-11-02 07:25:12 |
| Message-ID: | 1509607512.2750.76.camel@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I am afraid the changes may separate "7.a" to "7" and "a", then error
> out
> with "invalid input syntax for type int" for "a".
Which is correct, is it not?
> How about changes as below? (use following the if to decide true or
> false)
> ...
> return false;
> + } while (isdigit(**scan_length));
Yes, this is certainly correct and better than what I committed. What
was I thinking yesterday?
I think the same function is used for identifying garbage in floats
which might ask for different logic. Let me check.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-11-02 07:36:58 | Re: pg_basebackup fails on Windows when using tablespace mapping |
| Previous Message | Pavel Stehule | 2017-11-02 07:19:57 | Re: SQL/JSON in PostgreSQL |