Phil S wrote:
> I am running Postgresql on a Windows Server 2008 server. I have noticed that
> queries have very high
> planning times now and then. Planning times go down for the same query
> immediately after the query
> runs the first time, but then go up again after if the query is not re-run
It can be because of catalog stats file leak. I had it on some older
PostgreSQL version when tests were rolling back schema changes often. The
file grew to some enormous size and as soon as it got out of cache - it
would be very slow to access catalog. I had just to kill the file.
Best regards, Vi
Albe Laurenz writes:
> Phil S wrote:
>> explain analyze
>> select * from message
>> limit 1
>>
>> "Limit (cost=0.00..0.44 rows=1 width=1517) (actual time=0.009..0.009 rows=1
>> loops=1)"
>> " -> Seq Scan on message (cost=0.00..28205.48 rows=64448 width=1517)
>> (actual time=0.007..0.007
>>
