Re: Problem with collector statistic
От | Marco Aurélio V. da Silva |
---|---|
Тема | Re: Problem with collector statistic |
Дата | |
Msg-id | 000801c842f9$c17e29e0$0402a8c0@marquinho обсуждение исходный текст |
Ответ на | Problem with collector statistic (Marco Aurélio V. da Silva <marcoprodata@gmail.com>) |
Список | pgsql-general |
Dear, Thanks, this solved my problem. I was using very low values for effective_cache_size. Thanks for your attention, Marco Aurélio V. da Silva Prodata Inf. e Cad. Ltda. MSN: marco@prodatanet.com.br Fone: (33) 3322-3082 ----- Original Message ----- From: "Scott Marlowe" <scott.marlowe@gmail.com> To: "Marco Aurélio V. da Silva" <marcoprodata@gmail.com> Cc: "Tom Lane" <tgl@sss.pgh.pa.us>; <pgsql-general@postgresql.org> Sent: Wednesday, December 19, 2007 4:16 PM Subject: Re: [GENERAL] Problem with collector statistic On Dec 19, 2007 2:06 PM, Marco Aurélio V. da Silva <marcoprodata@gmail.com> wrote: > Sorry, > > I discovered that the problem appears to be another, doing tests with the > same database, this is a consultation limit using the same database and > with > 9364 records of the problem, and with 9363 not of. Sounds like pgsql is switching to a sequential scan a little too quickly for your dataset / server / etc... I'd say look at increasing effective_cache_size and lowering random_page_cost
В списке pgsql-general по дате отправления: