From: | Wei Weng <wweng(at)kencast(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: performance of insert/delete/update |
Date: | 2002-11-21 22:23:57 |
Message-ID: | 1037917437.5930.7.camel@Monet |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Thu, 2002-11-21 at 16:23, Josh Berkus wrote:
> Wei,
>
> > There had been a great deal of discussion of how to improve the
> > performance of select/sorting on this list, what about
> > insert/delete/update?
> >
> > Is there any rules of thumb we need to follow? What are the
> > parameters
> > we should tweak to whip the horse to go faster?
>
> yes, lots of rules. Wanna be more specific? You wondering about
> query structure, hardware, memory config, what?
I am most concerned about the software side, that is query structures
and postgresql config.
Thanks
--
Wei Weng
Network Software Engineer
KenCast Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-11-21 22:26:40 | Re: performance of insert/delete/update |
Previous Message | Christopher Kings-Lynne | 2002-11-21 21:59:53 | Re: Optimizer & boolean syntax |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-11-21 22:26:40 | Re: performance of insert/delete/update |
Previous Message | Bjoern Metzdorf | 2002-11-21 21:57:59 | Re: [ADMIN] H/W RAID 5 on slower disks versus no raid on |