Re: [PERFORM] Bulk loading/merging

USING clip_category WHERE clip_temp.cids=clip_category.cids AND clip_temp.clip_id=clip_category.clip_id   INSERT INTO clip_category (cids, clip_id, mentions) SELECT * FROM clip_temp   DROP TABLE clip_temp;     Best regards, ahmad fajar,        

Re: [PERFORM] serious problems with vacuuming databases

n't have to do a difficult database maintainance like you have done. You just need to create tables for every week of data, do vacuum/analyze and regular backup. Best regards, ahmad fajar, ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [PERFORM] Multiple Order By Criteria

Btree will not suffer, and we also will advantage if the table have relationship with other table with the same fields order. We have not to make another index for that relation. Best regards, ahmad fajar. > I am getting an idea of what I need to do to make this work well. I was > wonde

Re: [PERFORM] Text/Varchar performance...

search uses the index you have been created. If you do not need to index the field, you can use the text field. Because text field can store data up to 4 Gbytes. Regards, ahmad fajar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cristian Prieto Sent

Re: [PERFORM] Query seem to slow if table have more than 200 million rows

_ops), keywords (idx_dict3 varchar_pattern_ops) ==> I use this index for query ... keywords like 'blabla%', just for testing purpose Regards, ahmad fajar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Qingqing Zhou Sent: Selasa, 27 September 200

Re: [PERFORM] tsearch2 seem very slow

Hi Oleg, Thanks, I will read your documentation again, and try to understand what I miss. And about pgmanual, it is very help me. I'll take attention on that. Regards, ahmad fajar -Original Message- From: Oleg Bartunov [mailto:[EMAIL PROTECTED] Sent: Monday, September 26, 2005 3:

Re: [PERFORM] tsearch2 seem very slow

7;t know how to get it. > I try to cluster the table base on keyword index, but after 15 hours > waiting and it doesn't finish I stop clustering. > don't use cluster for big tables ! simple > select * into clustered_foo from foo order by indexed_fi

[PERFORM] Query seem to slow if table have more than 200 million rows

cation and same data, mssql server beat postgresql, the query about 0-4 sec to get the result. What wrong with my postgresql.   wassalam, ahmad fajar  

Re: [PERFORM] tsearch2 seem very slow

to change the file system for postgresql data. Do you have any idea what best for postgresql, JFS or XFS? I will not try reiserfs, because there are some rumors about reiserfs stability, although reiserfs is fast enough for postgresql. And must I down grade my postgresql from version 8.0.3 to

Re: [PERFORM] tsearch2 seem very slow

r I configure just only for postgresql, no other service is running like: www, samba, ftp, email, firewall hardware configuration: Motherboard ASUS P5GD1 Processor P4 3,2 GHz Memory 2 GB DDR 400, 2x200 GB Serial ATA 7200 RPM UltraATA/133, configure as RAID0 for postgresql da

[PERFORM] tsearch2 seem very slow

I have about 419804 rows in my article table. I have installed tsearch2 and its gist index correctly. My table structure is: CREATE TABLE tbarticles (   articleid int4 NOT NULL,   title varchar(250),   mediaid int4,   datee date,   content text,   contentvar text,   mmcol float4