From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Christopher Browne" <cbbrowne(at)acm(dot)org> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: [SQL] OFFSET impact on Performance??? |
Date: | 2005-01-27 14:35:09 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3412A75EC@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> Actually, you can if you assume you can "temporarily materialize" that
> view.
>
> Then, you use a join on my_query to pull the bits you want:
>
> select [big table.details] from [big table],
> [select * from my_query order by [something] offset 280 limit 20]
> where [join criteria between my_query and big table]
> order by [something];
>
I think that's a pretty reasonable compromise between a true
materialized solution and brute force limit/offset. Still, the
performance of a snapshot materialized view indexed around your query
simply can't be beat, although you have to pay a hefty price in
complexity, maintenance, and coherency.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Mitch Pirtle | 2005-01-27 14:50:32 | Re: SQL Performance Guidelines |
Previous Message | Oleg Bartunov | 2005-01-27 13:44:04 | Re: [SQL] OFFSET impact on Performance??? |