From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve <cheetah(at)tanabi(dot)org> |
Cc: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Strangely Variable Query Performance |
Date: | 2007-04-12 22:01:41 |
Message-ID: | 9213.1176415301@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches pgsql-performance |
Steve <cheetah(at)tanabi(dot)org> writes:
> Here's the table and it's indexes. Before looking, a note; there's
> several 'revop' indexes, this is for sorting. The customer insisted on,
> frankly, meaninglessly complicated sorts. I don't think any of that
> matters for our purposes here though :)
Oy vey ... I hope this is a read-mostly table, because having that many
indexes has got to be killing your insert/update performance.
I see that some of the revop indexes might be considered relevant to
this query, so how exactly have you got those opclasses defined?
There's built-in support for reverse sort as of CVS HEAD, but in
existing releases you must have cobbled something together, and I wonder
if that could be a contributing factor ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Steve | 2007-04-12 22:03:47 | Re: Strangely Variable Query Performance |
Previous Message | Jason Lustig | 2007-04-12 21:58:49 | Re: Slow Postgresql server |
From | Date | Subject | |
---|---|---|---|
Next Message | Steve | 2007-04-12 22:03:47 | Re: Strangely Variable Query Performance |
Previous Message | Jason Lustig | 2007-04-12 21:58:49 | Re: Slow Postgresql server |
From | Date | Subject | |
---|---|---|---|
Next Message | Steve | 2007-04-12 22:03:47 | Re: Strangely Variable Query Performance |
Previous Message | Jason Lustig | 2007-04-12 21:58:49 | Re: Slow Postgresql server |