=?ISO-8859-1?Q?Fabr=EDcio_dos_Anjos_Silva?=
writes:
> explain analyze select max(cnpj) from empresa where dtcriacao >=
> current_date-5;
> QUERY
> PLAN
> -
Samuel Gendler wrote:
As to your question about increasing shared_buffers to be some
significant proportion of available RAM - apparently, that is not a
good idea. I've seen advice that said you shouldn't go above 8GB for
shared_buffers and I've also seen 12GB suggested as an upper limit,
too
Fabrício dos Anjos Silva wrote:
After reading lots of documentation, I still don't understand fully
how PG knows if some needed data is in memory or in second storage.
While choosing the best query plan, the optimizer must take this into
account. Does PG consider this? If so, how does it know?
Craig Ringer wrote:
If some kind of cache awareness was to be added, I'd be interested in
seeing a "hotness" measure that tracked how heavily a given
relation/index has been accessed and how much has been read from it
recently. A sort of age-scaled blocks-per-second measure that includes
both
Fabrício dos Anjos Silva wrote:
Is there any automated test tool? A can compile a list of real-world
queries, and provide an exact copy of my db server just for testing.
But how do I do it? Write a bunch of scripts? Is there any serious
tool that try different parameters, run a load test, proce
Fabrício dos Anjos Silva wrote:
If someone could point good books about PG tuning, I would appreciate
that. I found some yet to be released books about PG 9. Any comments
about them?
The largest treatment of the subject already in print I'm aware of is in
the Korry and Susan Douglas "PostgreS
