Quoting Vivek Khera <[EMAIL PROTECTED]>:
> > "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
>
> TL> Jack Orenstein <[EMAIL PROTECTED]> writes:
> >> I'm looking at one case in which two successive transactions, each
> >> updating a handful of records, take 26 and 18 *seconds* (not msec) to
> >>
Quoting Rob Fielding <[EMAIL PROTECTED]>:
> Assuming you're running with optimal schema and index design (ie you're
> not doing extra work unnecessarily), and your backend has
> better-then-default config options set-up (plenty of tips around here),
> then disk arrangement is critical to smooth
My company is developing a PostgreSQL application. We're using 7.3.4
but will soon upgrade to 7.4.x. Our OS is RedHat 9. Our production
machines have 512 MB RAM and IDE disks. So far we've been using
default configuration settings, but I have started to examine
performance and to modify these sett
