Skip site navigation (1) Skip section navigation (2)

Re: BUG #6186: out of memory while analyze

From: Lampa <lampacz(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6186: out of memory while analyze
Date: 2011-08-31 05:25:50
Message-ID: CAG_XuNVY-dqhJHLj9WTuPqnA7Uta=+2HfUdqenuoRxnXDa5-Jg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Hello,

table design http://pastebin.com/RW6vLAVP

And configuration:

ssl = false
shared_buffers = 900MB                  # min 128kB
work_mem = 100MB                                # min 64kB
maintenance_work_mem = 524MB            # min 1MB
fsync = off                             # turns forced synchronization on or off
synchronous_commit = off                # immediate fsync at commit
full_page_writes = off                  # recover from partial page writes
effective_cache_size = 1GB
default_statistics_target = 8000        # range 1-10000


Also tried change maintenance_work_mem to 2G and same result.
Imposible to set over 2GB (FATAL:  3145728 is outside the valid range
for parameter "maintenance_work_mem" (1024 .. 2097151))

Problem seems to be in default_statistics_target values from approx
6300. Up to 6300 analyze works but on another machine (64bit) works
10000 without problems on same but larger table (more data)

2011/8/30 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Lampa" <lampacz(at)gmail(dot)com> writes:
>> Trying analyze table (ANALYZE TABLE table or VACUUM ANALYZE table) with
>> 3051316 rows (displayed size 2521MB in \dt+)
>
> What have you got maintenance_work_mem set to?  shared_buffers might
> also be interesting.
>
>                        regards, tom lane
>



-- 
Lampa

In response to

Responses

pgsql-bugs by date

Next:From: John R PierceDate: 2011-08-31 06:14:41
Subject: Re: BUG #6186: out of memory while analyze
Previous:From: Tom LaneDate: 2011-08-30 19:21:20
Subject: Re: BUG #6186: out of memory while analyze

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group