RE: [Bug Fix] ECPG: could not use set xxx to default statement
Higuchi, Daisuke <higuchi.daisuke@jp.fujitsu.com>
From: "Higuchi, Daisuke" <higuchi.daisuke@jp.fujitsu.com>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>, Michael Meskes <meskes@postgresql.org>
Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2019-02-19T09:38:01Z
Lists: pgsql-hackers
Attachments
- FIX_ECPG_SET_TO_DEFAULT_v2.patch (application/octet-stream) patch v2
Hi, > I think we need to fix that script to either cope with missing semicolons, > or at least complain about them. Too tired to look into how, right now. I attached the patch which cope with missing semicolons. Previous parse.pl find semicolon and dump data to buffer. When attached patch's parse.pl find new tokens before finding a semicolon, it also dumps data to buffer. Regards, Daisuke, Higuchi
Commits
-
Fix ecpg bugs caused by missing semicolons in the backend grammar.
- 53c2bb78db9f 9.4.22 landed
- 3a682a21b7f9 9.5.17 landed
- de94ed89d5b0 11.3 landed
- 9e138a401d19 12.0 landed
- 904fce2a7695 9.6.13 landed
- 8ec638e69c01 10.8 landed