On 08.10.2012 17:56, Tom Lane wrote:
> Andrzej Zawadzki writes:
>> On 08.10.2012 16:52, Tom Lane wrote:
>>> [ counts... ] You've got nine base relations in that query. I think
>>> you need to increase from_collapse_limit and/or join_collapse_limit.
>> Bingo! Thank you!
>> But... looks like in 9.
Andrzej Zawadzki writes:
> On 08.10.2012 16:52, Tom Lane wrote:
>> [ counts... ] You've got nine base relations in that query. I think
>> you need to increase from_collapse_limit and/or join_collapse_limit.
> Bingo! Thank you!
> But... looks like in 9.0 this worked differently or option was sk
On 08.10.2012 16:52, Tom Lane wrote:
> Andrzej Zawadzki writes:
>> I have no idea whats wrong. Looks like planer bad decision.
> [ counts... ] You've got nine base relations in that query. I think
> you need to increase from_collapse_limit and/or join_collapse_limit.
>
Bingo! Thank you!
But... l
Andrzej Zawadzki writes:
> I have no idea whats wrong. Looks like planer bad decision.
[ counts... ] You've got nine base relations in that query. I think
you need to increase from_collapse_limit and/or join_collapse_limit.
regards, tom lane
--
Sent via pgsql-perform
On 08.10.2012 12:15, Craig Ringer wrote:
> On 10/08/2012 04:18 PM, Andrzej Zawadzki wrote:
>> Hi!
>>
>> After upgrade (dump/restore/analyze) query (below) after some time is
>> killed by kernel.
>
> What's `shared_buffers`? `work_mem`?
shared_buffers = 64MB
work_mem = 48MB
effective_cache_size = 51
On 10/08/2012 04:18 PM, Andrzej Zawadzki wrote:
Hi!
After upgrade (dump/restore/analyze) query (below) after some time is killed by
kernel.
What's `shared_buffers`? `work_mem`?
https://wiki.postgresql.org/wiki/Server_Configuration
https://wiki.postgresql.org/wiki/Slow_Query_Questions
--
Cr
Hi!
After upgrade (dump/restore/analyze) query (below) after some time is killed by
kernel.
Postgres creates a lot of tmp files:
temporary file: path "base/pgsql_tmp/pgsql_tmp8949.2046", size 24576
temporary file: path "base/pgsql_tmp/pgsql_tmp8949.2045", size 24576
temporary file: path "base/pg