Re: BUG #6186: out of memory while analyze
От | Lampa |
---|---|
Тема | Re: BUG #6186: out of memory while analyze |
Дата | |
Msg-id | CAG_XuNVY-dqhJHLj9WTuPqnA7Uta=+2HfUdqenuoRxnXDa5-Jg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #6186: out of memory while analyze (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #6186: out of memory while analyze
Re: BUG #6186: out of memory while analyze Re: BUG #6186: out of memory while analyze |
Список | pgsql-bugs |
Hello, table design http://pastebin.com/RW6vLAVP And configuration: ssl =3D false shared_buffers =3D 900MB # min 128kB work_mem =3D 100MB # min 64kB maintenance_work_mem =3D 524MB # min 1MB fsync =3D off # turns forced synchronization on= or off synchronous_commit =3D off # immediate fsync at commit full_page_writes =3D off # recover from partial page writes effective_cache_size =3D 1GB default_statistics_target =3D 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@sss.pgh.pa.us>: > "Lampa" <lampacz@gmail.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? =C2=A0shared_buffers might > also be interesting. > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0regards, tom lane > --=20 Lampa
В списке pgsql-bugs по дате отправления: