From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Modify pg_dump to use error-free memory allocation macros. This |
Date: | 2011-11-26 14:11:09 |
Message-ID: | 201111261411.pAQEB9o15748@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
\Andrew Dunstan wrote:
>
>
> On 11/26/2011 02:13 AM, Tom Lane wrote:
> > Bruce Momjian<bruce(at)momjian(dot)us> writes:
> >> Modify pg_dump to use error-free memory allocation macros. This avoids
> >> ignoring errors and call-site error checking.
> > This appears to have broken the MSVC build. More generally, I'd like to
> > object to arbitrarily moving a bunch of longstanding code from one file
> > to another. What that is mainly going to accomplish is creating a big
> > headache whenever we have to back-patch fixes that touch that code
> > ... and what exactly did it buy in return?
> >
> >
>
>
> Was there any discussion of this change? It seems much too big for
> something to be done without discussion, but I don't recall seeing
> anything. (And it's probably seriously broken two patches I have in the
> commitfest).
The patch was posted Novembrer 14 and received no replies:
http://archives.postgresql.org/pgsql-hackers/2011-11/msg00860.php
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-11-26 14:18:36 | Re: pgsql: Modify pg_dump to use error-free memory allocation macros. This |
Previous Message | Andrew Dunstan | 2011-11-26 13:20:24 | Re: pgsql: Modify pg_dump to use error-free memory allocation macros. This |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-11-26 14:18:36 | Re: pgsql: Modify pg_dump to use error-free memory allocation macros. This |
Previous Message | Andrew Dunstan | 2011-11-26 13:20:24 | Re: pgsql: Modify pg_dump to use error-free memory allocation macros. This |