Re: Fwd: REWRITE_INVOKE_MAX and "query may contain cycles"
От | Tom Lane |
---|---|
Тема | Re: Fwd: REWRITE_INVOKE_MAX and "query may contain cycles" |
Дата | |
Msg-id | 1438.1045786279@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Fwd: REWRITE_INVOKE_MAX and "query may contain cycles" (Eric B.Ridge <ebr@tcdi.com>) |
Ответы |
Re: Fwd: REWRITE_INVOKE_MAX and "query may contain cycles"
|
Список | pgsql-general |
"Eric B. Ridge" <ebr@tcdi.com> writes: > That's better. I've set mine (in 7.2.3) to 1024. I'm at 50ish > operations right now and that number has the potential to grow, perhaps > even past 100. That's why I was asking if it could become a > configuration setting. Hm, I had figured "100 is plenty". But maybe not. > Is making it configurable technically possible (ie, can rewriteHandler > access GUC parameters?), and if I invested the time to make it happen, > would a patch be accepted? Yes, and yes IMHO. Even better would be to detect loops directly and eliminate this kluge entirely, but I'm not sure if you want to get into that ... whereas a GUC parameter is pretty trivial. Don't forget the documentation updates (which you will find is a bigger patch than the actual code change). regards, tom lane
В списке pgsql-general по дате отправления: