Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit0471eb1

Browse files
committed
Because we ended up forcing an initdb for 7.0 final, we aren't going
to need this updatepgproc.sql script after all...
1 parentc0337ec commit0471eb1

File tree

3 files changed

+2
-38
lines changed

3 files changed

+2
-38
lines changed

‎contrib/likeplanning/README

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
This directory containsthree SQL scripts that control use of some new
1+
This directory containstwo SQL scripts that control use of some new
22
code for planning/optimizing queries containing LIKE and
33
regular-expression operators. This code was added to Postgres 7.0 late in
44
beta test, and it hasn't gotten enough testing to warrant turning it on by
@@ -11,7 +11,7 @@ queries involving LIKE or regexps in WHERE clauses.
1111
HOW TO USE THE SCRIPTS
1212
----------------------
1313

14-
All three scripts must be run as the Postgres superuser. The easiest
14+
Both scripts must be run as the Postgres superuser. The easiest
1515
way to run an SQL script is
1616
psql -f scriptfile databasename
1717
or you can start psql interactively and enter
@@ -25,13 +25,6 @@ disablelike.sql reverts to the old planning code for LIKE, in the database
2525
in which it is run. If you run it in template1, all subsequently-created
2626
databases will use the old code by default.
2727

28-
If your database was initdb'd with release 7.0beta5, you need to run
29-
updatepgproc.sql before you can run enablelike.sql. Databases initdb'd
30-
with 7.0RC1 or later already have pg_proc entries for the new code, so
31-
updatepgproc.sql is unnecessary for them. If enablelike.sql produces
32-
errors like "No procedure with name regexeqsel", then you need to run
33-
updatepgproc.sql.
34-
3528

3629
WHAT IT DOES
3730
------------

‎contrib/likeplanning/enablelike.sql

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,6 @@
22
-- functions, which are a little too new to be enabled by default in 7.0.
33
-- You can disable them again by running disablelike.sql.
44

5-
-- If your database was initdb'd with 7.0beta5, you need to run
6-
-- updatepgproc.sql first. You can tell that is necessary if this
7-
-- script produces errors like "No procedure with name regexeqsel".
8-
95
-- Use of the functions will be enabled only in those databases you
106
-- run this script in. If you run it in template1,
117
-- all subsequently-created databases will use the functions.

‎contrib/likeplanning/updatepgproc.sql

Lines changed: 0 additions & 25 deletions
This file was deleted.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp