On 12.07.2007, at 04:19, Miguel Arroz wrote:
PostgreSQL manual, chapter 11, the section about multi-column
indexes. I realized, after further testing, that the planner tries
to re-arrange the order. But I think there are situations where the
planner may choose one or another column because there's no
"optimum" solution, and that choice comes from the order of the
args. But I'm not sure about any os this, I don't know a lot about
DBs, and I hate them more everyday.
Don't bother with multicolumn indexes for the start - you can add
them when you really need them. The other thing with PostgreSQL is:
turn on autovacuum so you have up to date statistics. Then you should
be safe for while.
You turn on autovaccum by using these settings in postgresql.conf:
stats_start_collector = on
stats_row_level = on
autovacuum = on
And always keep in mind:
1. Make it work.
2. Make it right.
3. Make it fast.
The other way around brings your project to an early death as you
will normally never finish it.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
