Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-05 Thread Alex Deucher
Ok, well, I dropped the DB and reloaded it and now all seems to be fine and performing well. I'm not sure what was going on before. Thanks for everyone's help! Alex On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: On 4/3/07, Tom Lane <[EMAIL PROTECTED]> wrote: > "Alex Deucher" <[EMAIL PROTEC

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Alex Deucher
On 4/3/07, Tom Lane <[EMAIL PROTECTED]> wrote: "Alex Deucher" <[EMAIL PROTECTED]> writes: > Turning off bitmapscan ends up doing a sequential scan. Turning off > both bitmapscan and seqscan results in a bitmap heap scan. It doesn't > seem to want to use the index at all. Any ideas? The "ORed

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Alex Deucher
On 4/3/07, Tom Lane <[EMAIL PROTECTED]> wrote: "Alex Deucher" <[EMAIL PROTECTED]> writes: > Turning off bitmapscan ends up doing a sequential scan. Turning off > both bitmapscan and seqscan results in a bitmap heap scan. It doesn't > seem to want to use the index at all. Any ideas? The "ORed

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Alex Deucher
On 4/3/07, Tom Lane <[EMAIL PROTECTED]> wrote: "Alex Deucher" <[EMAIL PROTECTED]> writes: > Turning off bitmapscan ends up doing a sequential scan. Turning off > both bitmapscan and seqscan results in a bitmap heap scan. It doesn't > seem to want to use the index at all. Any ideas? The "ORed

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Tom Lane
"Alex Deucher" <[EMAIL PROTECTED]> writes: > Turning off bitmapscan ends up doing a sequential scan. Turning off > both bitmapscan and seqscan results in a bitmap heap scan. It doesn't > seem to want to use the index at all. Any ideas? The "ORed indexscans" plan style that was in 7.4 isn't ther

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Alex Deucher
On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: > On 4/3/07, Merlin Moncure <[EMAIL PROTECTED]> wrote: > > On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: > > (('{AB6698130,AB7076908,AB6499382,AB643,AB6385893,AB6378237,AB7146973,AB7127

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Alex Deucher
On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: On 4/3/07, Merlin Moncure <[EMAIL PROTECTED]> wrote: > On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: > (('{AB6698130,AB7076908,AB6499382,AB643,AB6385893,AB6378237,AB7146973,AB7127138,AB7124531,AB7124513,AB7123427,AB7121183,AB7121036,AB7

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Alex Deucher
On 4/3/07, Merlin Moncure <[EMAIL PROTECTED]> wrote: On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: (('{AB6698130,AB7076908,AB6499382,AB643,AB6385893,AB6378237,AB7146973,AB7127138,AB7124531,AB7124513,AB7123427,AB7121183,AB7121036,AB7110101,AB7100321,AB7089845,AB7088750,AB7031384,AB7021188

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Merlin Moncure
On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: (('{AB6698130,AB7076908,AB6499382,AB643,AB6385893,AB6378237,AB7146973,AB7127138,AB7124531,AB7124513,AB7123427,AB7121183,AB7121036,AB7110101,AB7100321,AB7089845,AB7088750,AB7031384,AB7021188,AB7006144,AB6988331,AB6973865,AB6966775,AB6935066,AB6

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Alex Deucher
On 4/3/07, Alex Deucher <[EMAIL PROTECTED]> wrote: On 4/3/07, Tom Lane <[EMAIL PROTECTED]> wrote: > "Alex Deucher" <[EMAIL PROTECTED]> writes: > > and here are the query plans referenced in my last email (apologies if > > you get these twice, they didn't seem to go through the first time, > > per

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-03 Thread Alex Deucher
On 4/3/07, Tom Lane <[EMAIL PROTECTED]> wrote: "Alex Deucher" <[EMAIL PROTECTED]> writes: > and here are the query plans referenced in my last email (apologies if > you get these twice, they didn't seem to go through the first time, > perhaps due to size?). I cut out the longer ones. The first

Re: [PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-02 Thread Tom Lane
"Alex Deucher" <[EMAIL PROTECTED]> writes: > and here are the query plans referenced in my last email (apologies if > you get these twice, they didn't seem to go through the first time, > perhaps due to size?). I cut out the longer ones. The first case looks a whole lot like 8.2 does not think it

[PERFORM] postgres 7.4 vs 8.x redux: query plans

2007-04-02 Thread Alex Deucher
and here are the query plans referenced in my last email (apologies if you get these twice, they didn't seem to go through the first time, perhaps due to size?). I cut out the longer ones. Thanks, Alex postgres 7.4 EXPLAIN ANALYZE select num, c1, c2, c3, c4, c5, c6, c7, c8, c9, c10, c11 from

[PERFORM] postgres 7.4 vs. 8.x redux

2007-04-02 Thread Alex Deucher
Sorry if anyone receives this twice; it didn't seem to go through the first time. I'll attach the query plans to another email in case they were causing a size limit problem. Also here's the here's the table description: Table "public.t1" Column | Type | Modifiers