Re: plpython is broken for recursive use
От | Josh Berkus |
---|---|
Тема | Re: plpython is broken for recursive use |
Дата | |
Msg-id | 5620179F.6060102@agliodbs.com обсуждение исходный текст |
Ответ на | plpython is broken for recursive use (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: plpython is broken for recursive use
Re: plpython is broken for recursive use |
Список | pgsql-hackers |
On 10/15/2015 01:10 PM, Tom Lane wrote: > I think this means that we should get rid of proc->globals and instead > manufacture a new globals dict locally in each call to PLy_exec_function > or PLy_exec_trigger. For SETOF functions it would be necessary to keep > the globals dict reference somewhere in the FunctionCallInfo struct, > probably. Not sure about cleaning up after an error that occurs between > SETOF callbacks --- we might need plpython to grow an at-abort callback to > do decref's on unreleased dicts. Don't people currently specifically treat the state of the globals dict as a feature? That is, make use of the fact that you can store session-persistent data in it? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
В списке pgsql-hackers по дате отправления: