mirror of
https://github.com/postgres/postgres.git
synced 2025-12-19 17:02:53 +03:00
spell checker run
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.117 2007/10/26 01:11:09 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.118 2007/11/28 15:42:31 petere Exp $ -->
|
||||
|
||||
<chapter id="plpgsql">
|
||||
<title><application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language</title>
|
||||
@@ -3348,7 +3348,7 @@ SELECT * INTO myrec FROM dictionary WHERE word LIKE search_term;
|
||||
where <literal>search_term</> is a <application>PL/pgSQL</application>
|
||||
variable. The cached plan for this query will never use an index on
|
||||
<structfield>word</>, since the planner cannot assume that the
|
||||
<literal>LIKE</> pattern will be left-anchored at runtime. To use
|
||||
<literal>LIKE</> pattern will be left-anchored at run time. To use
|
||||
an index the query must be planned with a specific constant
|
||||
<literal>LIKE</> pattern provided. This is another situation where
|
||||
<command>EXECUTE</command> can be used to force a new plan to be
|
||||
|
||||
Reference in New Issue
Block a user