Re: perfomance question/issues - Mailing list pgsql-general

From Tom Lane
Subject Re: perfomance question/issues
Date
Msg-id 13827.1035246798@sss.pgh.pa.us
Whole thread Raw
In response to Re: perfomance question/issues  ("Williams, Travis L, NPONS" <tlw@att.com>)
List pgsql-general
"Williams, Travis L, NPONS" <tlw@att.com> writes:
> What I have is 4 static columns that are indexed and roughly 460 that
> are updated.  Now I have only 215 rows.  If I update all of the columns
> then run vacuum analyze it takes 7-10 minutes.   I also have had trouble
> doing updates... I have tried doing them through perl and psql by doing
> a \i then the file name.. I have also tried using begin; and end; around
> the file.. but it still takes 1 minute+ to update one row.

That's a lot 'o columns.  Resisting for the moment the temptation to
suggest that your database design needs rethinking, I wonder whether you
are running into some performance bottleneck associated with either
lots-of-columns per se, or TOAST needing to squeeze down many columns in
order to fit the rows into blocks.  What datatypes are you using in this
table?  Do you have any idea about the average width of the rows?

            regards, tom lane

pgsql-general by date:

Previous
From: "Williams, Travis L, NPONS"
Date:
Subject: Re: perfomance question/issues
Next
From: Jean-Christian Imbeault
Date:
Subject: test