On Tue, Sep 17, 2019 at 4:41 AM Bob Jolliffe wrote:
> Hi
>
> We are trying to diagnose why postgres might be making poor decisions
> regarding query plans. One theory is that it does not assume it has
> the memory suggested in effective_cache_size.
> We do know that max_connections is set quit
Thanks Tom. Will check that.
On Tue, 17 Sep 2019 at 14:13, Tom Lane wrote:
>
> Bob Jolliffe writes:
> > We do know that max_connections is set quite high (600) when we don't
> > really expect more than 100. I wonder does the planner take
> > max_connections x work_mem into account when conside
Bob Jolliffe writes:
> We do know that max_connections is set quite high (600) when we don't
> really expect more than 100. I wonder does the planner take
> max_connections x work_mem into account when considering the memory it
> has potentially available?
No. There have been discussions to the
Hi
We are trying to diagnose why postgres might be making poor decisions
regarding query plans. One theory is that it does not assume it has
the memory suggested in effective_cache_size.
We do know that max_connections is set quite high (600) when we don't
really expect more than 100. I wonder
