Re: pg11+: pg_ls_*dir LIMIT 1: temporary files .. not closed atend-of-transaction
От | Alvaro Herrera |
---|---|
Тема | Re: pg11+: pg_ls_*dir LIMIT 1: temporary files .. not closed atend-of-transaction |
Дата | |
Msg-id | 20200312124917.GA8369@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: pg11+: pg_ls_*dir LIMIT 1: temporary files .. not closed atend-of-transaction (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: pg11+: pg_ls_*dir LIMIT 1: temporary files .. not closed at end-of-transaction
|
Список | pgsql-hackers |
Nitpick: please see c4dcd9144ba6. > From: Justin Pryzby <pryzbyj@telsasoft.com> > Date: Wed, 11 Mar 2020 10:09:18 -0500 > Subject: [PATCH] SRF: avoid leaking resources if not run to completion > > Change to return a tuplestore populated immediately and returned in full. > > Discussion: https://www.postgresql.org/message-id/20200308173103.GC1357%40telsasoft.com I wonder if this isn't saying that the whole value-per-call protocol is bogus, in that it seems impossible to write a useful function with it. Maybe we should add one final call with a special flag "function shutdown" or something, so that these resources can be released if the SRF isn't run to completion? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: