Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: how does pg handle concurrent queries and same queries
- From: "Dennis Brakhane" <brakhane(at)googlemail(dot)com>
- To: "Faludi Gábor" <gfaludi(at)fits(dot)hu>
- Cc: pgsql-performance(at)postgresql(dot)org
- Subject: Re: how does pg handle concurrent queries and same queries
- Date: Wed, 30 Jul 2008 20:34:16 +0200
- Message-id: <226a19190807301134p188cf6d7gaf829b10430629aa@mail.gmail.com> <text/plain>
Slightly off-topic, but judging from the fact that you were able to "fix" the query, it seems you have some way to modify the application code itself. In that case, I'd try to implement caching (at least for this statement) on the application side, for example with memcached.
- References:
- how does pg handle concurrent queries and same queries
- From: Faludi Gábor
- how does pg handle concurrent queries and same queries
- Prev by Date: Re: Database size Vs performance degradation
- Next by Date: Re: Database size Vs performance degradation
- Previous by thread: Re: how does pg handle concurrent queries and same queries
- Next by thread: Database size Vs performance degradation
- Indexes: