| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Wang, Shenhao" <wangsh(dot)fnst(at)cn(dot)fujitsu(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: errors when there is a bit literal in ecpg |
| Date: | 2020-11-07 20:05:42 |
| Message-ID: | 1753027.1604779542@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Wang, Shenhao" <wangsh(dot)fnst(at)cn(dot)fujitsu(dot)com> writes:
> I met an error as below when I use ecpg
> a.pgc:5: ERROR: invalid bit string literal
> a.pgc:5: ERROR: internal error: unreachable state; please report this to <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Indeed. This has apparently been broken for a very long time (though
the "unreachable state" part is fairly new).
> I try to fix this bug by deleting 'addlitchar('b');' from source I also add a test case to test all const str in ecpg.
I thought that a whole new test case was overkill when we could just add a
couple of lines to an existing test. Other than that, looks good, pushed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-11-07 20:38:28 | Re: WIP: BRIN multi-range indexes |
| Previous Message | Erik Rijkers | 2020-11-07 19:15:07 | Re: Additional Chapter for Tutorial |