aboutsummaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2002-06-25 01:45:58 +0000
committerBruce Momjian <bruce@momjian.us>2002-06-25 01:45:58 +0000
commit0b584830f0efef400ef26da58e5c17f14cece3e7 (patch)
treeee4148746fac76beaceb33422e17c9b210fa619c /doc/FAQ
parent6918df16a5483600fb0466b96f813ed5b6927fd8 (diff)
downloadpostgresql-0b584830f0efef400ef26da58e5c17f14cece3e7.tar.gz
postgresql-0b584830f0efef400ef26da58e5c17f14cece3e7.zip
Update FAQ.
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/FAQ b/doc/FAQ
index a1f9d150ba7..0cc05b3d3b7 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Sun Jun 23 17:16:13 EDT 2002
+ Last updated: Mon Jun 24 21:45:50 EDT 2002
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -743,13 +743,14 @@
using an index with ORDER BY and LIMIT:
SELECT col
FROM tab
- ORDER BY col
+ ORDER BY col [ DESC ]
LIMIT 1
When using wild-card operators such as LIKE or ~, indexes can only be
- used if the beginning of the search is anchored to the start of the
- string. Therefore, to use indexes, LIKE patterns must not start with
- %, and ~(regular expression) patterns must start with ^.
+ used if the default C local is used during initdb and the beginning of
+ the search is anchored to the start of the string. Therefore, to use
+ indexes, LIKE patterns must not start with %, and ~(regular
+ expression) patterns must start with ^.
4.9) How do I see how the query optimizer is evaluating my query?