Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'src/backend/regex/README')
-rw-r--r--src/backend/regex/README8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/backend/regex/README b/src/backend/regex/README
index 5c24d3dfe9d..6c9f48315e3 100644
--- a/src/backend/regex/README
+++ b/src/backend/regex/README
@@ -332,10 +332,10 @@ The possible arc types are:
as "$0->to_state" or "$1->to_state" for end-of-string and end-of-line
constraints respectively.
- LACON constraints, which represent "(?=re)" and "(?!re)" constraints,
- i.e. the input starting at this point must match (or not match) a
- given sub-RE, but the matching input is not consumed. These are
- dumped as ":subtree_number:->to_state".
+ LACON constraints, which represent "(?=re)", "(?!re)", "(?<=re)", and
+ "(?<!re)" constraints, i.e. the input starting/ending at this point must
+ match (or not match) a given sub-RE, but the matching input is not
+ consumed. These are dumped as ":subtree_number:->to_state".
If you see anything else (especially any question marks) in the display of
an arc, it's dumpnfa() trying to tell you that there's something fishy