Search Postgresql Archives

SLOOOOOOOW

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

I working now for a wile with postgres (7.4), and I have the impression
that is one of the slowest dbms with which I've aver worked. Can please
somebody explain to me, why this is the case?

I mean, the flexibility postgres offers is great, and I really
appreciate it. But if you take advantage of this it is just nearly
unusable because it is so slow. For instance I have some views, which
gather some data from a few tables, and in several occasions there are
other views operation on these views. It is f.... slow. And I have
already created indices and the query are using these indices. 

It can't be tha case, that a few queries, already optimzed, have such a
lousy performance. And I'm only talking about select statements. For
insert statements the performance is even worse. OK, I'm using rules on
a view to update some tables, but hey, it cant be that updating 1
(one!!!) record takes around 3 seconds, thats unusable!

With best regards
Juergen Rose

---------------------------(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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux