Skip site navigation (1) Skip section navigation (2)

Re: pg_dump on Postgres 9.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alanoly Andrews <alanolya(at)invera(dot)com>
Cc: "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_dump on Postgres 9.1
Date: 2012-08-03 20:01:58
Message-ID: 10180.1344024118@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Alanoly Andrews <alanolya(at)invera(dot)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(at)sss(dot)pgh(dot)pa(dot)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

In response to

pgsql-admin by date

Next:From: Scott MarloweDate: 2012-08-03 20:05:25
Subject: Re: PostgreSQL oom_adj postmaster process to -17
Previous:From: Kevin GrittnerDate: 2012-08-03 19:03:19
Subject: Re: PostgreSQL oom_adj postmaster process to -17

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group