| 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: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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 | Date | Subject | |
|---|---|---|---|
| Next Message | Clarence Ho | 2018-11-09 04:51:52 | Re: Strange corruption in psql output on mereswine |
| Previous Message | Pavel Stehule | 2018-11-09 04:07:52 | Re: PostgreSQL vs SQL/XML Standards |