Hello,
/proc/sys/vm/swappiness = 60
/proc/sys/vm/overcommit_memory = 0
/proc/sys/vm/overcommit_ratio = 50
total used free sharedbuffers cached
Mem: 4038 3146892 0 30 3067
-/+ buffers/cache: 49 3989
Sw
>
>
> 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
Hi Lampa,
On Thu, Sep 1, 2011 at 6:26 AM, Lampa wrote:
> With default value 100 have bad perfomance :-(
Don't set the default value higher: specify a higher value only where needed.
See ALTER TABLE ALTER [ COLUMN ] column SET STATISTICS integer (
http://www.postgresql.org/docs/9.0/interactive/s
Hello,
ok or write that there is limit for 32bit system.
With default value 100 have bad perfomance :-(
But thank you for yours time.
2011/8/31 Tom Lane :
> Lampa writes:
>> default_statistics_target = 8000 # range 1-1
>
>> Problem seems to be in default_statistics_target values fro
Lampa writes:
> default_statistics_target = 8000# range 1-1
> Problem seems to be in default_statistics_target values from approx
> 6300. Up to 6300 analyze works but on another machine (64bit) works
> 1 without problems on same but larger table (more data)
Well, there's a reason
On 08/30/11 10:25 PM, Lampa wrote:
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))
is this a 32bit postgres ?
--
john r pierce
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
"Lampa" 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
--
Sent via pgsql-bugs ma
On 30.08.2011 14:20, Lampa wrote:
Trying analyze table (ANALYZE TABLE table or VACUUM ANALYZE table) with
3051316 rows (displayed size 2521MB in \dt+)
Log:
...
Analyze: 2236767256 total in 279 blocks; 18080 free (423 chunks);
2236749176 used
> ...
Hmm, that looks like a memory like in A
The following bug has been logged online:
Bug reference: 6186
Logged by: Lampa
Email address: lamp...@gmail.com
PostgreSQL version: 9.0.4/8.4.8
Operating system: Linux Debian testing 32bit
Description:out of memory while analyze
Details:
Trying analyze table (ANALYZ
10 matches
Mail list logo
