Re: planner/optimizer question - Mailing list pgsql-performance

From Gary Doades
Subject Re: planner/optimizer question
Date
Msg-id 409172FA.1509.14C7E00E@localhost
Whole thread Raw
In response to Re: planner/optimizer question  ("Rosser Schwarz" <rschwarz@totalcardinc.com>)
Responses Re: planner/optimizer question  (Josh Berkus <josh@agliodbs.com>)
Re: planner/optimizer question  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
> It's also entirely possible your indices are using inaccurate
> statistical information.  Have you ANALYZEd recently?
>

In this example the statistics don't matter. The plans used were the same for
MSSQL and Postgres. I was trying to eliminate the difference in plans
between the two, which obviously does make a difference, sometimes in
MSSQL favour and sometimes the other way round. Both systems, having
decided to do the same index scan, took noticably different times. The
Postgres database was fully vacuumed and analysed anyway.

I agree about MSSQL recovery time. it sucks. This is why they are making a
big point about the improved recovery time in "yukon". Although the recovery
time is important, I see this as an exception, whereas at the moment I am
interested in the everyday.

Cheers,
Gary.


pgsql-performance by date:

Previous
From: "Rosser Schwarz"
Date:
Subject: Re: planner/optimizer question
Next
From: Josh Berkus
Date:
Subject: Re: planner/optimizer question