Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: High update activity, PostgreSQL vs BigDBMS
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Shoaib Mir" <shoaibmir(at)gmail(dot)com>
- Cc: "Guy Rouillier" <guyr-ml1(at)burntmail(dot)com>, "PostgreSQL Performance" <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: High update activity, PostgreSQL vs BigDBMS
- Date: Thu, 28 Dec 2006 09:56:54 -0500
"Shoaib Mir" <shoaibmir(at)gmail(dot)com> writes: > Here are my few recommendations that might help you: > [ snip good advice ] Another thing to look at is whether you are doing inserts/updates as individual transactions, and if so see if you can "batch" them to reduce the per-transaction overhead. regards, tom lane
- Follow-Ups:
- Re: High update activity, PostgreSQL vs BigDBMS
- From: Guy Rouillier
- Re: High update activity, PostgreSQL vs BigDBMS
- References:
- High update activity, PostgreSQL vs BigDBMS
- From: Guy Rouillier
- Re: High update activity, PostgreSQL vs BigDBMS
- From: Shoaib Mir
- High update activity, PostgreSQL vs BigDBMS
- Prev by Date: Re: Advice on selecting good values for work_mem?
- Next by Date: Postgresql Configutation and overflow
- Previous by thread: Re: High update activity, PostgreSQL vs BigDBMS
- Next by thread: Re: High update activity, PostgreSQL vs BigDBMS
- Indexes: