Re: COUNT & Pagination
От | David Shadovitz |
---|---|
Тема | Re: COUNT & Pagination |
Дата | |
Msg-id | 20040113174533.M77388@www.shadovitz.com обсуждение исходный текст |
Ответ на | Re: COUNT & Pagination (mallah@trade-india.com) |
Ответы |
Re: COUNT & Pagination
|
Список | pgsql-performance |
> We avert the subsequent execution of count(*) by passing the > value of count(*) as a query parameter through the link in page > numbers. Mallah, and others who mentioned caching the record count: Yes, I will certainly do this. I can detect whether the query's filter has been changed, or whether the user is merely paging through the results or sorting* the results. I'd love to completely eliminate the cost of the COUNT(*) query, but I guess that I cannot have everything. * My HTML table column headers are hyperlinks which re-execute the query, sorting the results by the selected column. The first click does an ASC sort; a second click does a DESC sort. Thanks. -David
В списке pgsql-performance по дате отправления: