Re: too many clients already

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: too many clients already
Дата
Msg-id
20255.1585845622@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
too many clients already "Abraham, Danny" <danny_abraham@bmc.com>
Re: too many clients already Tom Lane <tgl@sss.pgh.pa.us>
RE: Re: too many clients already "Abraham, Danny" <danny_abraham@bmc.com>
Re: too many clients already Tom Lane <tgl@sss.pgh.pa.us>
RE: Re: too many clients already "Abraham, Danny" <danny_abraham@bmc.com>
Re: too many clients already Rob Sargent <robjsargent@gmail.com>
RE: Re: too many clients already "Abraham, Danny" <danny_abraham@bmc.com>
Re: too many clients already Adrian Klaver <adrian.klaver@aklaver.com>
RE: Re: too many clients already "Abraham, Danny" <danny_abraham@bmc.com>
Re: too many clients already Adrian Klaver <adrian.klaver@aklaver.com>
RE: Re: too many clients already "Abraham, Danny" <danny_abraham@bmc.com>
Re: too many clients already Adrian Klaver <adrian.klaver@aklaver.com>
"Abraham, Danny"  writes:
> Well, I guess the questions is - how do I optimize PG for a stream of very short life checks...

You should be using a connection pooler for a load like that.
PG backends are fairly heavyweight things --- you don't want
to fire one up for just a single query, at least not when
there are many such queries per second.

I think pgbouncer and pgpool are the most widely used options,
but this is a bit outside my expertise.

			regards, tom lane


В списке pgsql-general по дате отправления
От: Abraham, Danny
Дата:
От: Abraham, Danny
Дата:
FAQ