Re: Identifying a message in emit_log_hook.
От | Kyotaro HORIGUCHI |
---|---|
Тема | Re: Identifying a message in emit_log_hook. |
Дата | |
Msg-id | 20160315.122205.08265186.horiguchi.kyotaro@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: Identifying a message in emit_log_hook. (David Steele <david@pgmasters.net>) |
Ответы |
Re: Identifying a message in emit_log_hook.
|
Список | pgsql-hackers |
Thnak you for scooping up this. At Thu, 10 Mar 2016 08:14:09 -0500, David Steele <david@pgmasters.net> wrote in <56E17321.5050201@pgmasters.net> > Hi Simon, > > On 3/10/16 7:26 AM, Simon Riggs wrote: > > > > Can you add this to the CF? It was submitted before deadline. > > I presume you have access to do that? > > No problem - here it is: > > https://commitfest.postgresql.org/9/576/ Some kind of hash code can be added for shotrcut, but this is usable even after it is added. One arguable point I see now on this is only ids for the message type "message" would be enough, or needed for some other types such as "details". This is quite straightforward so I see no other arguable point other than the code itself. regards, -- Kyotaro Horiguchi NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: