Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
0471cd5f
Commit
0471cd5f
authored
Jan 09, 2005
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify description of greedy and non-greedy POSIX regular expressions,
per discussion in Nov 2004 with Ken Tanzer.
parent
a9566ccc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
94 additions
and
30 deletions
+94
-30
doc/src/sgml/func.sgml
doc/src/sgml/func.sgml
+94
-30
No files found.
doc/src/sgml/func.sgml
View file @
0471cd5f
<!--
<!--
$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.23
3 2005/01/08 05:19:18
tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.23
4 2005/01/09 20:08:50
tgl Exp $
PostgreSQL documentation
PostgreSQL documentation
-->
-->
...
@@ -3772,45 +3772,109 @@ substring('foobar' from 'o(.)b') <lineannotation>o</lineannotation>
...
@@ -3772,45 +3772,109 @@ substring('foobar' from 'o(.)b') <lineannotation>o</lineannotation>
In the event that an RE could match more than one substring of a given
In the event that an RE could match more than one substring of a given
string, the RE matches the one starting earliest in the string.
string, the RE matches the one starting earliest in the string.
If the RE could match more than one substring starting at that point,
If the RE could match more than one substring starting at that point,
its choice is determined by its <firstterm>preference</>:
either the longest possible match or the shortest possible match will
either the longest substring, or the shortest.
be taken, depending on whether the RE is <firstterm>greedy</> or
<firstterm>non-greedy</>.
</para>
</para>
<para>
<para>
Most atoms, and all constraints, have no preference.
Whether an RE is greedy or not is determined by the following rules:
A parenthesized RE has the same preference (possibly none) as the RE.
<itemizedlist>
A quantified atom with quantifier
<listitem>
<literal>{</><replaceable>m</><literal>}</>
<para>
or
Most atoms, and all constraints, have no greediness attribute (because
<literal>{</><replaceable>m</><literal>}?</>
they cannot match variable amounts of text anyway).
has the same preference (possibly none) as the atom itself.
</para>
A quantified atom with other normal quantifiers (including
</listitem>
<literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</>
<listitem>
with <replaceable>m</> equal to <replaceable>n</>)
<para>
prefers longest match.
Adding parentheses around an RE does not change its greediness.
A quantified atom with other non-greedy quantifiers (including
</para>
<literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}?</>
</listitem>
with <replaceable>m</> equal to <replaceable>n</>)
<listitem>
prefers shortest match.
<para>
A branch has the same preference as the first quantified atom in it
A quantified atom with a fixed-repetition quantifier
which has a preference.
(<literal>{</><replaceable>m</><literal>}</>
An RE consisting of two or more branches connected by the
or
<literal>|</> operator prefers longest match.
<literal>{</><replaceable>m</><literal>}?</>)
has the same greediness (possibly none) as the atom itself.
</para>
</listitem>
<listitem>
<para>
A quantified atom with other normal quantifiers (including
<literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</>
with <replaceable>m</> equal to <replaceable>n</>)
is greedy (prefers longest match).
</para>
</listitem>
<listitem>
<para>
A quantified atom with a non-greedy quantifier (including
<literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}?</>
with <replaceable>m</> equal to <replaceable>n</>)
is non-greedy (prefers shortest match).
</para>
</listitem>
<listitem>
<para>
A branch — that is, an RE that has no top-level
<literal>|</> operator — has the same greediness as the first
quantified atom in it that has a greediness attribute.
</para>
</listitem>
<listitem>
<para>
An RE consisting of two or more branches connected by the
<literal>|</> operator is always greedy.
</para>
</listitem>
</itemizedlist>
</para>
<para>
The above rules associate greediness attributes not only with individual
quantified atoms, but with branches and entire REs that contain quantified
atoms. What that means is that the matching is done in such a way that
the branch, or whole RE, matches the longest or shortest possible
substring <emphasis>as a whole</>. Once the length of the entire match
is determined, the part of it that matches any particular subexpression
is determined on the basis of the greediness attribute of that
subexpression, with subexpressions starting earlier in the RE taking
priority over ones starting later.
</para>
<para>
An example of what this means:
<screen>
SELECT SUBSTRING('XY1234Z', 'Y*([0-9]{1,3})');
<lineannotation>Result: </lineannotation><computeroutput>123</computeroutput>
SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
<lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
</screen>
In the first case, the RE as a whole is greedy because <literal>Y*</>
is greedy. It can match beginning at the <literal>Y</>, and it matches
the longest possible string starting there, i.e., <literal>Y123</>.
The output is the parenthesized part of that, or <literal>123</>.
In the second case, the RE as a whole is non-greedy because <literal>Y*?</>
is non-greedy. It can match beginning at the <literal>Y</>, and it matches
the shortest possible string starting there, i.e., <literal>Y1</>.
The subexpression <literal>[0-9]{1,3}</> is greedy but it cannot change
the decision as to the overall match length; so it is forced to match
just <literal>1</>.
</para>
</para>
<para>
<para>
Subject to the constraints imposed by the rules for matching the whole RE,
In short, when an RE contains both greedy and non-greedy subexpressions,
subexpressions also match the longest or shortest possible substrings,
the total match length is either as long as possible or as short as
based on their preferences,
possible, according to the attribute assigned to the whole RE. The
with subexpressions starting earlier in the RE taking priority over
attributes assigned to the subexpressions only affect how much of that
ones starting later.
match they are allowed to <quote>eat</> relative to each other.
Note that outer subexpressions thus take priority over
their component subexpressions.
</para>
</para>
<para>
<para>
The quantifiers <literal>{1,1}</> and <literal>{1,1}?</>
The quantifiers <literal>{1,1}</> and <literal>{1,1}?</>
can be used to force
longest and shortest preference
, respectively,
can be used to force
greediness or non-greediness
, respectively,
on a subexpression or a whole RE.
on a subexpression or a whole RE.
</para>
</para>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment