summaryrefslogtreecommitdiff
path: root/Docs
diff options
context:
space:
mode:
authorunknown <arjen@fred.bitbike.com>2002-04-29 10:29:56 +1000
committerunknown <arjen@fred.bitbike.com>2002-04-29 10:29:56 +1000
commit472b1c107b9c464847961f8ad2e58f4f831acb0e (patch)
treee7eed0e9d74959d4390da7a91a542bcd8d3ac6f0 /Docs
parent17433fc12f1a30ede9dc0be21e97a59149a7f2a6 (diff)
downloadmariadb-git-472b1c107b9c464847961f8ad2e58f4f831acb0e.tar.gz
Re-added note about R-trees in PostgreSQL (noting MySQL 4.1 support too).
Diffstat (limited to 'Docs')
-rw-r--r--Docs/manual.texi4
1 files changed, 4 insertions, 0 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi
index 90176ee7946..199bdebc5e5 100644
--- a/Docs/manual.texi
+++ b/Docs/manual.texi
@@ -4969,6 +4969,10 @@ Standard usage in PostgreSQL is closer to ANSI SQL in some cases.
One can speed up PostgreSQL by coding things as stored procedures.
@item
+For geographical data, R-trees make PostgreSQL better than MySQL Server.
+(note: MySQL version 4.1 will have R-trees for MyISAM tables).
+
+@item
The PostgreSQL optimiser can do some optimisation that the current MySQL
optimiser can't do. Most notable is doing joins when you don't have the
proper keys in place and doing a join where you are using different keys