Re: Error in recent pg_dump change (coverity) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Error in recent pg_dump change (coverity)
Date
Msg-id 18285.1148836026@sss.pgh.pa.us
Whole thread Raw
In response to Re: Error in recent pg_dump change (coverity)  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Error in recent pg_dump change (coverity)  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> Hm.  But I think we'd *like* it to segfault; the idea is to make the
>> user's programming error as obvious as possible.  Is it worth the
>> trouble to just zero out the pointer members of the PGresult?

> There are only five of them; four need to be zeroed out.

Works for me.  Please commit, as I'm about to do some further work in
those files and would rather not have to merge ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Error in recent pg_dump change (coverity)
Next
From: Alvaro Herrera
Date:
Subject: Re: Error in recent pg_dump change (coverity)