Re: [PERFORM] Limit & offset effect on query plans

2012-12-13 Thread Kevin Grittner
Tom Lane wrote: > Huh, so on a percentage basis the Limit-node overhead is actually > pretty significant, at least for a trivial seqscan plan like this > case. (This is probably about the worst-case scenario, really, > since it's tough to beat a simple seqscan for cost-per-emitted- > row. Also I g

Re: [PERFORM] Limit & offset effect on query plans

2012-12-13 Thread Tom Lane
"Kevin Grittner" writes: > Tom Lane wrote: >> 1.35ms out of what? > Without the limit node the runtimes (after "priming" the cache) > were: > 1.805, 2.533 > 1.805, 2.495 > 1.800, 2.446 > 1.818, 2.470 > 1.804, 2.502 > The first time for each run is "Total runtime" reported by EXPLAIN, > the seco

Re: [PERFORM] Limit & offset effect on query plans

2012-12-13 Thread Kevin Grittner
Tom Lane wrote: > "Kevin Grittner" writes: >> I ran some quick tests on my i7 under Linux. Plan time was >> increased by about 40 microseconds (based on EXPLAIN runtime) >> and added a limit node to the plan. Execution time on a SELECT * >> FROM tenk1 in the regression database went up by 1.35 ms

Re: [PERFORM] Limit & offset effect on query plans

2012-12-13 Thread Tom Lane
"Kevin Grittner" writes: > Pavan Deolasee wrote: >> I would tend to think that is the latter. While undoubtedly >> limit/offset clause will add another node during query planning >> and execution, AFAICS the OFFSET 0 and LIMIT ALL cases are >> optimized to a good extent. So the overhead of having

Re: [PERFORM] Limit & offset effect on query plans

2012-12-13 Thread Kevin Grittner
Pavan Deolasee wrote: > Amitabh Kant wrote: >> Our scripts automatically add "LIMIT ALL" & "OFFSET 0" to every >> select query if no values are passed on for these parameters. I >> remember reading through the mailing list that it's better not >> to pass them if they are not needed as they add a

Re: [PERFORM] Limit & offset effect on query plans

2012-12-12 Thread Pavan Deolasee
On Thu, Dec 13, 2012 at 9:38 AM, Amitabh Kant wrote: > Hi > > Our scripts automatically add "LIMIT ALL" & "OFFSET 0" to every select query > if no values are passed on for these parameters. I remember reading through > the mailing list that it's better not to pass them if they are not needed as >

[PERFORM] Limit & offset effect on query plans

2012-12-12 Thread Amitabh Kant
Hi Our scripts automatically add "LIMIT ALL" & "OFFSET 0" to every select query if no values are passed on for these parameters. I remember reading through the mailing list that it's better not to pass them if they are not needed as they add a cost to the query plan. Is this the case, or am i loo