From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Reuven M(dot) Lerner" <reuven(at)lerner(dot)co(dot)il> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Database slowness -- my design, hardware, or both? |
Date: | 2007-03-06 05:04:17 |
Message-ID: | 26820.1173157457@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Reuven M. Lerner" <reuven(at)lerner(dot)co(dot)il> writes:
> Hi, everyone. I've been using PostgreSQL for a decade, and it hasn't
> failed me yet. But I've been having some serious performance problems
> on a database that I've been using in my grad-school research group, and
> it's clear that I need help from some more experienced hands.
What PG version are you using?
> In theory, this would be the way to go. In practice, every step has
> become a performance nightmare, taking many more hours than I might have
> hoped or expected. For example, I've got a Pl/PgSQL function that goes
> through each variable-assignment row, and UPDATEs is previous_value
> column with whatever the previous value might have been.
I'd try to think of a way to eliminate the function altogether in favor
of a single UPDATE command. In general, row-at-a-time thinking isn't
the way to win in SQL.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Reuven M. Lerner | 2007-03-06 05:22:12 | Re: Database slowness -- my design, hardware, or both? |
Previous Message | Reuven M. Lerner | 2007-03-06 04:54:09 | (no subject) |