| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Marko Kreen <markokr(at)gmail(dot)com>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [9.2] crash on regex |
| Date: | 2012-05-24 17:56:39 |
| Message-ID: | 26558.1337882199@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thom Brown <thom(at)linux(dot)com> writes:
> Hmmm... curiously, lazy (non-greedy) quantifiers are stable, such as: ((a))*?
I've found it. The triggering conditions are (1) more than one set of
capturing parens in a substring() pattern, and (2) at least one trial
midpoint failing in ccondissect() or one of its siblings. That results
in zaptreesubs() trying to clear an array entry that isn't there...
trivial to fix fortunately. So it's not so much what the quantifiers
are as whether the first attempted match succeeds.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-05-24 17:58:39 | Re: shared_preload_libraries path |
| Previous Message | Sergey Koposov | 2012-05-24 17:42:33 | Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile |