Re: WIP patch: convert SQL-language functions to return tuplestores
| От | Gregory Stark |
|---|---|
| Тема | Re: WIP patch: convert SQL-language functions to return tuplestores |
| Дата | |
| Msg-id | 87k5btc921.fsf@oxford.xeocode.com обсуждение исходный текст |
| Ответ на | Re: WIP patch: convert SQL-language functions to return tuplestores (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: WIP patch: convert SQL-language functions to return tuplestores
|
| Список | pgsql-hackers |
Tom Lane <tgl@sss.pgh.pa.us> writes: > "Robert Haas" <robertmhaas@gmail.com> writes: >> I'm pretty excited by that example. LIMIT/OFFSET is really useful as >> a way of paginating query results for display on a web page (show >> results 1-100, 101-200, etc), and I use it on potentially expensive >> SRFs just as I do on tables and views. > > I suspect it doesn't help you as much as you think. It's always been > the case that SRFs in FROM-items are fed through a tuplestore, and so > are plpgsql SRF results. I always thought we considered that a bug though. It sure would be nice if we could generate results as needed instead of having to generate them in advance and store all of them. In particular I fear there are a lot of places that use functions where we might expect them to use views. They're never going to get really good plans but it would be nice if we could at least avoid the extra materialize steps. Now your patch isn't affecting that one way or the other but does it rule it out forever? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!
В списке pgsql-hackers по дате отправления: