| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Gary Doades" <gpd(at)gpdnet(dot)co(dot)uk>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL and Linux 2.6 kernel. |
| Date: | 2004-04-03 18:59:39 |
| Message-ID: | 200404031059.39268.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Gary,
> There are no indexes on the columns involved in the update, they are
> not required for my usual select statements. This is an attempt to
> slightly denormalise the design to get the performance up comparable
> to SQL Server 2000. We hope to move some of our databases over to
> PostgreSQL later in the year and this is part of the ongoing testing.
> SQLServer's query optimiser is a bit smarter that PostgreSQL's (yet)
> so I am hand optimising some of the more frequently used
> SQL and/or tweaking the database design slightly.
Hmmm ... that hasn't been my general experience on complex queries. However,
it may be due to a difference in ANALYZE statistics. I'd love to see you
increase your default_stats_target, re-analyze, and see if PostgreSQL gets
"smarter".
--
-Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gary Doades | 2004-04-03 19:32:35 | Re: PostgreSQL and Linux 2.6 kernel. |
| Previous Message | Palle Girgensohn | 2004-04-03 13:24:07 | Re: single index on more than two coulumns a bad thing? |