Closed M-Butter closed 10 months ago
should be fixed by 463ac3acf402ad716cc533851058b0a8ad0d4c6d commit.
You are first man who used empty string there in my 20 years work with plpgsql :-).
Hello Pavel,
The problem originates from a migrated Oracle procedure that contained an execute immediate 'create table ...' statement. Our migration software decided that the create table statement needed extra attention, so commented it out inside the create table string. The empty string was just a simplified version of that, which caused the same problem.
Thanks for fixing, Martin.
st 22. 11. 2023 v 13:37 odesílatel M-Butter @.***> napsal:
Hello Pavel,
The problem originates from a migrated Oracle procedure that contained an execute immediate 'create table ...' statement. Our migration software decided that the create table statement needed extra attention, so commented it out inside the create table string. The empty string was just a simplified version of that, which caused the same problem.
Thanks for fixing,
Thank you for report
Pavel
Martin.
— Reply to this email directly, view it on GitHub https://github.com/okbob/plpgsql_check/issues/161#issuecomment-1822694648, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEFO47Y3WMULTYGRS5D6W3YFXWZHAVCNFSM6AAAAAA7VZGGLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRSGY4TINRUHA . You are receiving this because you commented.Message ID: @.***>
When I have a procedure that contains an EXECUTE statement with an empty string ('') as argument, or just comment ('--') as argument, and I run plpgsql_check on that function, then a segmentation fault is the result:
From the server log: