| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Mathieu Nebra <mateo21(at)siteduzero(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How would you store read/unread topic status? |
| Date: | 2009-06-23 15:04:28 |
| Message-ID: | 603c8f070906230804od43a415j5e96789edd73ecb9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>> > Which pg version are you using?
>
> I should have mentionned that before sorry: PostgreSQL 8.2
I think there is an awful lot of speculation on this thread about what
your problem is without anywhere near enough investigation. A couple
of seconds for an update is a really long time, unless your server is
absolutely slammed, in which case probably everything is taking a long
time. We need to get some more information on what is happening here.
Approximately how many requests per second are you servicing? Also,
can you:
1. Run EXPLAIN ANALYZE on a representative UPDATE statement and post
the exact query and the output.
2. Run VACUUM VERBOSE on your database and send the last 10 lines or
so of the output.
3. Try your UPDATE statement at a low-traffic time of day and see
whether it's faster than it is at a high-traffic time of day, and by
how much. Or dump your database and reload it on a dev server and see
how fast it runs there.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Cottenceau | 2009-06-23 15:11:55 | Re: How would you store read/unread topic status? |
| Previous Message | Mathieu Nebra | 2009-06-23 15:00:08 | Re: How would you store read/unread topic status? |