notice processors for isolationtester

Lists: pgsql-hackers
From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: notice processors for isolationtester
Date: 2018-10-24 21:34:51
Message-ID: 20181024213451.75nh3f3dctmcdbfq@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgsql-hackers

Recently while testing a patch I found it immensely useful to
distinguish which session each WARNING message came from, when bespoke
tests were run under isolationtester. Current code does not show that,
so I developed this patch adding notice processors, and then it does.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
isolationtester-notices.patch text/x-diff 9.6 KB

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: notice processors for isolationtester
Date: 2018-10-24 21:38:54
Message-ID: 20181024213854.ac6tflq3gn4ll4ul@alap3.anarazel.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgsql-hackers

On 2018-10-24 18:34:51 -0300, Alvaro Herrera wrote:
> Recently while testing a patch I found it immensely useful to
> distinguish which session each WARNING message came from, when bespoke
> tests were run under isolationtester. Current code does not show that,
> so I developed this patch adding notice processors, and then it does.

Neat!


From: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: notice processors for isolationtester
Date: 2018-11-09 04:17:38
Message-ID: CAJrrPGeTy=xWX2Ai3dT3e5+k10fy_H_XVd6BGGH60zhxX0hxaQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, Oct 25, 2018 at 8:35 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:

> Recently while testing a patch I found it immensely useful to
> distinguish which session each WARNING message came from, when bespoke
> tests were run under isolationtester. Current code does not show that,
> so I developed this patch adding notice processors, and then it does.
>

I reviewed and tested the patch. It is working as expected.
Providing session name helps in debugging.

Marking the patch as ready for committer.

Regards,
Haribabu Kommi
Fujitsu Australia


From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: notice processors for isolationtester
Date: 2018-11-09 16:16:24
Message-ID: 20181109161624.7oe5hx3erpcreihq@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgsql-hackers

On 2018-Nov-09, Haribabu Kommi wrote:

> On Thu, Oct 25, 2018 at 8:35 AM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
> wrote:
>
> > Recently while testing a patch I found it immensely useful to
> > distinguish which session each WARNING message came from, when bespoke
> > tests were run under isolationtester. Current code does not show that,
> > so I developed this patch adding notice processors, and then it does.
>
> I reviewed and tested the patch. It is working as expected.
> Providing session name helps in debugging.
>
> Marking the patch as ready for committer.

Thanks! Pushed.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services