Re: [PATCH] SQL function to report log message
От | Robert Haas |
---|---|
Тема | Re: [PATCH] SQL function to report log message |
Дата | |
Msg-id | CA+TgmoY=zk125mOWjrwTkyTJ8VEQ+2_VsPJoTpQRG7fc0rAT-Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] SQL function to report log message (Jeff Janes <jeff.janes@gmail.com>) |
Ответы |
Re: [PATCH] SQL function to report log message
Re: [PATCH] SQL function to report log message |
Список | pgsql-hackers |
This patch is marked as Ready for Committer in the CommitFest application. Here is my attempt to summarize the votes upthread: Tom Lane: plpgsql RAISE is sufficient; we don't need this. Pavel Stehule: could be replaced by custom function, but not against it. Robert Haas: plpgsql RAISE is sufficient; we don't need this. Jim Nasby: A generic wrapper around RAISE is not trivial, so +1. Andres Freund: I've written this function many times, so let's have it in core. David Fetter: I've written this function like 20 times, we should have it. I'm only -0 on this patch, so I won't yell and scream if some other committer is prepared to step up and get this committed, but I'm not excited about doing it myself on the strength of a weak consensus in which I'm not a participant. Any takers? I recommend that we allow this patch 30 days to attract an interested committer, and, if nobody volunteers in that time, that we mark it Rejected for lack of interest. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: