Re: [PERFORM] pg 9.1 brings host machine down

. hth, Patric Vitalii Tymchyshyn schrieb am 06.06.2012 14:25: Hello. Seen this already. It looks like cross join + sort. Badly configured ORM tools like Hibernate with multiple one-to-many relationships fetched with 'join' strategy may produce such result. Unfortunately I don't know

[PERFORM] Reasonable amount of indices

want partition with method postgres offers..) thanks in advance, patric ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do

[PERFORM] Vacuum full considered useful ;)

of diskspace. Now after a fresh import it only has 5 gigabyte! No wonder, I got IO problems with such a fragmentation. For people not very familiar with postgres especially those coming from mysql, i'd recommend paying attention to this. regards, patric de waha

[PERFORM] Two questions.. shared_buffers and long reader issue

. Patric My Setup: Debian Etch PSQL: 8.1.4 WAL files are located on another disc than the dbase itself. max_connections = 190 shared_buffers = 3 temp_buffers = 3000 work_mem = 4096 maintenance_work_mem = 16384 fsync

Re: [PERFORM] Two questions.. shared_buffers and long reader issue

Ok thanks. iostat confirmed it's an IO bottleneck. Will add some discs to the RAID unit. Used 4 Raptor discs in Raid 10 until now. best regards, patric Tom Lane wrote: Patric de Waha [EMAIL PROTECTED] writes: Postgres is running on a dedicated server P4 DualCore, 4 Gig Ram