Re: Identifying a message in emit_log_hook.

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: david(at)pgmasters(dot)net
Cc: simon(at)2ndQuadrant(dot)com, pavel(dot)stehule(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Identifying a message in emit_log_hook.
Date: 2016-03-22 04:57:42
Message-ID: 20160322.135742.27731310.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I found that this has been commited.
Thank you for committing this, Simon.

regards,

At Tue, 15 Mar 2016 12:22:05 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote in <20160315(dot)122205(dot)08265186(dot)horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
> Thnak you for scooping up this.
>
> At Thu, 10 Mar 2016 08:14:09 -0500, David Steele <david(at)pgmasters(dot)net> wrote in <56E17321(dot)5050201(at)pgmasters(dot)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.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-03-22 05:06:04 Re: Relax requirement for INTO with SELECT in pl/pgsql
Previous Message Dilip Kumar 2016-03-22 04:57:04 Re: Move PinBuffer and UnpinBuffer to atomics