Re: pg_dump vs malloc

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump vs malloc
Date: 2011-11-25 20:41:36
Message-ID: 201111252041.pAPKfaW06329@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> I developed the attached patch to handle this. I moved the catalog code
> from common.c into dumpcatalog.c, so there are just memory routines now
> in common.c. I created new memory routines in pg_dumpall.c because
> there is no AH structure in pg_dumpall.c. I then modified all the calls
> to use the new routines, and removed the NULL return checks that were no
> longer necessary.

Applied.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2011-11-25 20:53:19 Re: Inserting heap tuples in bulk in COPY
Previous Message Bruce Momjian 2011-11-25 20:41:27 pgsql: Modify pg_dump to use error-free memory allocation macros. This