Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs?

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs?
Дата
Msg-id CABUevEzCqAzNYUN7ZNmGvrJjqemA6sdUn5r4GokmzxrszLePzw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Should we have an optional limit on the recursion depth of recursive CTEs?  (Greg Stark <stark@mit.edu>)
Ответы Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs?  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
On Mon, Aug 15, 2011 at 23:49, Greg Stark <stark@mit.edu> wrote:
> On Mon, Aug 15, 2011 at 9:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> ... and that would be a seriously bad API.  There are not SUSET
>> restrictions on other resources such as work_mem.  Why do we need
>> one for this?
>
> I think a better analogy would be imposing a maximum number of rows a
> query can output. That might be a sane thing to have for some
> circumstances but it's not useful in general.

Uh. You mean like LIMIT, which we already have?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Some problems about cascading replication
Следующее
От: Jeevan Chalke
Дата:
Сообщение: Allowing same cursor name in nested levels