Re: Two small patches for the isolationtester lexer
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2018-02-28T22:01:08Z
Lists: pgsql-hackers
Daniel Gustafsson <daniel@yesql.se> writes: > On 22 Feb 2018, at 05:10, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Actually, looking closer, this would also trigger on '#' used inside a >> SQL literal, which seems to move the problem cases into the "pretty >> likely" category instead of the "far-fetched" one. So I'd only be OK >> with it if we made the lexer smart enough to distinguish inside-a-SQL- >> literal from not. That might be a good thing anyway, since it would >> allow us to not choke on literals containing '}', but it'd be a great >> deal more work. You might be able to steal code from the psql lexer >> though. > I agree, patch 0002 was broken and the correct fix is a much bigger project - > one too big for me to tackle right now (but hopefully at some point in the near > future). Thanks for the review of it though! OK. I'm going to mark this commitfest entry closed, since the other patch is in and this one needs a good bit more work. Please start a new thread, or at least a new CF entry, if you do more work in this area. regards, tom lane
Commits
-
Remove restriction on SQL block length in isolationtester scanner.
- e459eb9fb0c2 9.5.13 landed
- cadb14c271bf 9.4.18 landed
- 824cceded409 9.3.23 landed
- a030b997ae33 9.6.9 landed
- 38a1144a91d2 11.0 landed
- 14ffdd8cf88f 10.4 landed