Re: [EXTERNAL] Re: [PATCH] Report the query string that caused a memory error under Valgrind - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [EXTERNAL] Re: [PATCH] Report the query string that caused a memory error under Valgrind
Date
Msg-id 1222141.1680531589@sss.pgh.pa.us
Whole thread Raw
In response to RE: [EXTERNAL] Re: [PATCH] Report the query string that caused a memory error under Valgrind  (Onur Tirtir <Onur.Tirtir@microsoft.com>)
List pgsql-hackers
Onur Tirtir <Onur.Tirtir@microsoft.com> writes:
> Thank you for sharing your proposal as a patch. It looks much nicer and useful than mine.
> I've also tested it for a few cases --by injecting a memory error on purpose-- and seen that it helps reporting the
problematicquery. 
> Should we move forward with v3 then?

OK, I pushed v3 as-is.  We can refine it later if anyone has suggestions.

Thanks for the contribution!

            regards, tom lane



pgsql-hackers by date:

Previous
From: Pavel Borisov
Date:
Subject: Re: POC: Lock updated tuples in tuple_update() and tuple_delete()
Next
From: Robert Haas
Date:
Subject: Re: running logical replication as the subscription owner