_hans_

4 ms·

1. 1.▲
   PostgreSQL: CLUSTER table USING index;(hans.io)

   2 points by _hans_ 13y ago|1 comments
2. 2.▲
   by _hans_ 13y ago

   We do have this problem! It is only a matter of how small the PGBouncer machine is compared to the PostgreSQL. In our case the PGBouncer had to deal with 16000 req/s, coming from 700 clients going through 100 connections to the Postgre
3. 3.▲
   by _hans_ 13y ago

   Thank you. We configured the system to accept more file descriptors. I think our issue was caused by something else.
4. 4.▲
   by _hans_ 13y ago

   Neither AWS RDS PostgreSQL nor Heroku has a PGBouncer.
5. 5.▲
   by _hans_ 13y ago

   There was no apparent problem with turning it off for us. But maybe there is for others.
6. 6.▲
   by _hans_ 13y ago

   Yes you're right, idle connection do not use temp_buffers or work_mem. I was trying to gather everything relevant to resources per connection. I'm not saying work_mem caused our problem.
7. 7.▲
   by _hans_ 13y ago

   We enabled PGBouncer transaction mode and had to set 'prepared_statements: false' in our database.yml b/c the transaction mode doesn't support that. Works fine for us.
8. 8.▲
   by _hans_ 13y ago

   Thanks for your comment! Re work_mem: I think this is per query and thus might affect every connection?! At least thats what I gather from 'PostgreSQL 9.0 High Performance' Re temp_buffers: 'Sets the maximum number of tempora