From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
---|---|
To: | Alexander Farber <alexander(dot)farber(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 8.4.8 bringing my website down every evening |
Date: | 2011-06-17 06:46:50 |
Message-ID: | BB6AE395-DC38-4AD5-A829-F5DB307ABD61@solfertje.student.utwente.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 16 Jun 2011, at 21:42, Alexander Farber wrote:
> On 6/16/11, Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> wrote:
>> 2011/6/16 Alexander Farber <alexander(dot)farber(at)gmail(dot)com>:
>>> I'm still suffering with my Drupal 7.2 site and
>>> PostgreSQL 8.4.8 every evening, for example
>>> right now. I have tried different combinations
>>> for /etc/pgbouncer.ini - for example now I have:
>>>
>>> [pgbouncer]
>>> logfile = /var/log/pgbouncer.log
>>> pidfile = /var/run/pgbouncer/pgbouncer.pid
>>> ;listen_addr = 127.0.0.1
>>> listen_port = 6432
>>> unix_socket_dir = /tmp
>>>
>>> auth_type = md5
>>> auth_file = /var/lib/pgsql/data/global/pg_auth
>>>
>>> pool_mode = session
>>>
>>
>> you probably want to use transaction mode here, instead of session.
>>
>
> Is transaction mode better for PHP scripts with
> persistent connections? I'll try that, thank you
> (rebooting right now... GPRS sucks)
I think the intention was to use a pooler INSTEAD OF php persistent connections. Having both doesn't make sense to me.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4dfaf87012091396613445!
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2011-06-17 07:39:17 | Re: Postgres performance and the Linux scheduler |
Previous Message | Alban Hertroys | 2011-06-17 06:42:59 | Re: Constraint to ensure value does NOT exist in another table? |