| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jonathan Allen <jallen(at)americansavingslife(dot)com> |
| Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT |
| Date: | 2018-05-11 03:36:27 |
| Message-ID: | 28287.1526009787@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jonathan Allen <jallen(at)americansavingslife(dot)com> writes:
> I saw the release of v10.4 today and was very excited to try using the official version of ecpg, but unfortunately I'm getting the same "unsupported type "long long" on line x" error. SQL State: YE000, SQL Code: -200.
> ...did this fix not make it into the May release?
Well, we committed *something* about that:
Does that not match the fix you were using?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-05-11 14:26:23 | BUG #15193: Postgres Coredumped in AIX |
| Previous Message | Jonathan Allen | 2018-05-11 00:37:47 | RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT |