From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alanoly Andrews <alanolya@invera.com>
Cc: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: Re: pg_dump on Postgres 9.1
Date: Fri, 03 Aug 2012 16:01:58 -0400
Message-ID: <10180.1344024118@sss.pgh.pa.us> (raw)
In-Reply-To: <09B23E7BF70425478C1330D893A722C606F6088F07@MailSVR.invera.com>
References: <09B23E7BF70425478C1330D893A722C606F6088EE5@MailSVR.invera.com>
<5933.1343405558@sss.pgh.pa.us>
<09B23E7BF70425478C1330D893A722C606F6088F07@MailSVR.invera.com>
Alanoly Andrews <alanolya@invera.com> writes:
> On this issue, instead of going for a newer version of xlc, as suggested, I opted to get a newer version of the Postgres source code, 9.1.4. After compiling it with the same xlc version, I found that pg_dump works as expected. So, the problem appears to be somewhere in the 9.1 source code, at least for binaries created from it for AIX (6.1).
Hm, maybe this 9.1.2 fix?
Author: Tom Lane <tgl@sss.pgh.pa.us>
Branch: master Release: REL9_2_BR [cf22e851b] 2011-11-10 16:09:01 -0500
Branch: REL9_1_STABLE Release: REL9_1_2 [febda37fd] 2011-11-10 16:09:16 -0500
Avoid platform-dependent infinite loop in pg_dump.
If malloc(0) returns NULL, the binary search in findSecLabels() will
probably go into an infinite loop when there are no security labels,
because NULL-1 is greater than NULL after wraparound.
(We've seen this pathology before ... I wonder whether there's a way to
detect the class of bugs automatically?)
Diagnosis and patch by Steve Singer, cosmetic adjustments by me
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, alanolya@invera.com
Subject: Re: pg_dump on Postgres 9.1
In-Reply-To: <10180.1344024118@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox