Re: Slow query: bitmap scan troubles
postgresql@foo.me.uk
From: <postgresql@foo.me.uk>
To: "'postgres performance list'" <pgsql-performance@postgresql.org>
Date: 2012-12-04T18:54:29Z
Lists: pgsql-hackers, pgsql-performance
Ah, okay - my reasoning was there's a big fancy-pants raid array behind it that makes disk operations faster relative to CPU ones. I'll test it and see if it actually makes any difference. -----Original Message----- From: Claudio Freire [mailto:klaussfreire@gmail.com] Sent: 04 December 2012 18:33 To: Philip Scott Cc: postgresql@foo.me.uk; postgres performance list Subject: Re: [PERFORM] Slow query: bitmap scan troubles On Tue, Dec 4, 2012 at 3:31 PM, Philip Scott <pscott@foo.me.uk> wrote: > r_p_c 2-> 1 (s_p_c 1->0.5): Is this really necessary? (looks like a no-op, unless your CPU is slow)
Commits
-
Tweak genericcostestimate's fudge factor for index size.
- bf01e34b556f 9.3.0 cited
-
Tweak index costing for problems with partial indexes.
- 21a39de5809c 9.2.0 cited