Mark Woodward wrote: > Hmm, OK, then the problem is more serious than I suspected. > This means that every index on a row has to be updated on every > transaction that modifies that row. Is that correct?
Add an index entry, yes. > I am attaching some code that shows the problem with regard to > applications such as web server session management, when run, each second > the system can handle fewer and fewer connections. Here is a brief output: > [...] > There has to be a more linear way of handling this scenario. So vacuum the table often. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
