| From: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
|---|---|
| To: | Yan Chunlu <springrider(at)gmail(dot)com> |
| Cc: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: how could select id=xx so slow? |
| Date: | 2012-07-12 01:07:00 |
| Message-ID: | CAOtHd0Cq-hy1q1Mc8PW0MP8WMuztCsVHxGvU1z+B1xY5P6QkrA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Jul 11, 2012 at 5:47 PM, Yan Chunlu <springrider(at)gmail(dot)com> wrote:
> I learnt a lot during the back and forth!
Great to hear.
>> 1, postgresql always have 400+ connections(dozens of python process using client pool)
Note that Postgres does not deal well with a large number of
connections[1]: consider shrinking the size of the pool.
[1]: http://wiki.postgresql.org/wiki/Number_Of_Database_Connections
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2012-07-12 01:23:16 | Re: DELETE vs TRUNCATE explanation |
| Previous Message | Yan Chunlu | 2012-07-12 00:47:21 | Re: how could select id=xx so slow? |