| From: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Subject: | Re: Limit changes query plan |
| Date: | 2008-02-01 11:42:56 |
| Message-ID: | 47A305C0.4000900@bigfoot.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martijn van Oosterhout wrote:
> On Fri, Feb 01, 2008 at 12:08:56PM +0100, Gaetano Mendola wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi all,
>> I'm using 8.2.6 and I'm observing a trange behaviour using
>> offset and limits.
>
> Please post EXPLAIN ANALYZE output so we can see what's actually taking
> the time.
The analyze is still running (I launched it 30 mins ago), I'll post it as soon
I have it.
Disabling the nested_loop ( set enable_nestloop = false ) the query with the limit
has now the same execution time without the limit.
I don't get why a limit is going to change the query plan and most of all decreasing
the performances.
Regards
Gaetano Mendola
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHowXA7UpzwH2SGd4RAomqAJ409579Jk7d5FYWf92PjOYDRxWNIQCggg1w
1WJcVmn2g1MASBGh9OtCQ0Q=
=h2Z6
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-02-01 12:35:26 | Re: Limit changes query plan |
| Previous Message | Martijn van Oosterhout | 2008-02-01 11:16:09 | Re: Limit changes query plan |