Re: How would you store read/unread topic status? - Mailing list pgsql-performance

From Greg Stark
Subject Re: How would you store read/unread topic status?
Date
Msg-id 407d949e0906231244t5ed760d9ye3c8f9431fc4c20@mail.gmail.com
Whole thread Raw
In response to Re: How would you store read/unread topic status?  (Scott Carey <scott@richrelevance.com>)
Responses Re: How would you store read/unread topic status?
List pgsql-performance
All the other comments are accurate, though it does seem like
something the database ought to be able to handle.

The other thing which hasn't been mentioned is that you have a lot of
indexes. Updates require maintaining all those indexes. Are all of
these indexes really necessary? Do you have routine queries which look
up users based on their flags? Or all all your oltp transactions for
specific userids in which case you probably just need the index on
userid.

You'll probably find 8.3 helps this workload more than any tuning you
can do in the database though. Especially if you can reduce the number
of indexes and avoid an index on any flags that are being updated.

pgsql-performance by date:

Previous
From: Scott Carey
Date:
Subject: Re: How would you store read/unread topic status?
Next
From: Mike Ivanov
Date:
Subject: Implications of having large number of users