They're all valid, but most apply to versions < 8.0 or < 7.4 even, and
the others are pretty esoteric issues that you don't see often. The
missing from clause thing is likely to be the biggest surprise most
folks run into.
I find the supposed bad performance of aggregates is bunk. On my
workstation (not even a server, just my personal workstation with all
kinds of other crap running on it) I get a response time of about 1
second for a count(*) in version 7.4 of postgresql:
select count(*) from locators;
count
---------
1000000
(1 row)
takes anywhere from .75 to 1.0 second.
The same dataset, on oracle takes 0.75 seconds on a very fast oracle
server, and anywhere from 5 to 20 seconds on a slower server, like one
equivalent to my workstation.
On Thu, 2005-10-06 at 14:01, Aly S.P Dharshi wrote:
> No flamewar here, I am just trying to see if opinions of others on this,
> as Jim had posted a MySQL one, and that there was a PostgreSQL one, so I
> wanted to see if these are valid, if they aren't then that site should be
> updated to reflect this.
>
> Cheers,
>
> Aly.
>
> On Thu, 6 Oct 2005, Gavin M. Roy wrote:
>
> > This sure sounds like a flamewar bait email?
> >
> > On Oct 6, 2005, at 11:07 AM, Aly S.P Dharshi wrote:
> >
> >> http://sql-info.de/postgresql/postgres-gotchas.html
> >>
> >> Any comments from folks on the list ?
> >>
> >> Cheers,
> >>
> >> Aly.
> >>
> >> -- Aly S.P Dharshi
> >> aly.dharshi@telus.net
> >>
> >> "A good speech is like a good dress
> >> that's short enough to be interesting
> >> and long enough to cover the subject"
> >>
> >> ---------------------------(end of broadcast)---------------------------
> >> TIP 9: In versions below 8.0, the planner will ignore your desire to
> >> choose an index scan if your joining column's datatypes do not
> >> match
> >>
> >
> > Gavin M. Roy
> > 800 Pound Gorilla
> > gmr@ehpg.net
> >
> >