Postgres Pro
Downloads
Home   >   mailing lists

RE: [Bug Fix] ECPG: could not use set xxx to default statement - Mailing list pgsql-hackers

From Higuchi, Daisuke
Subject RE: [Bug Fix] ECPG: could not use set xxx to default statement
Date
Msg-id 1803D792815FC24D871C00D17AE95905DB551E@g01jpexmbkw24
Whole thread Raw
In response to Re: [Bug Fix] ECPG: could not use set xxx to default statement  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [Bug Fix] ECPG: could not use set xxx to default statement  (Michael Meskes <meskes@postgresql.org>)
Re: [Bug Fix] ECPG: could not use set xxx to default statement  (Michael Meskes <meskes@postgresql.org>)
List pgsql-hackers
Tree view 
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
asemicolon, it also dumps data to buffer.
 

Regards, 
Daisuke, Higuchi
Attachment

pgsql-hackers by date:

Previous
From: Michael Meskes
Date:
Subject: Re: [Bug Fix] ECPG: could not use set xxx to default statement
Next
From: Michael Paquier
Date:
Subject: Re: Prepared transaction releasing locks before deregistering its GID