Search Postgresql Archives

design help for performance

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

 



I am bumping into some performance issues and am seeking help.

I have two tables A and B in a one (A) to many (B) relationship.  There are 1.4 million records in table A and 44 million records in table B.  In my web application any request for a record from table A is also going to need a count of associated records in table B.  Several years ago I added table_b_rowcount to table A in order to minimize queries on table B.  And now, as the application has grown, I am starting to having locking problems on table A.  Any change to table B requires the that table_b_rowcount be updated on table A...  The application has outgrown this solution.

So... is there a common solution to this problem?

culley

[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