Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 5F176152A2F6 for ; Fri, 27 Jul 2012 13:12:56 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Sun9p-0002qd-So for pgsql-admin@postgresql.org; Fri, 27 Jul 2012 16:12:55 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q6RGCcqE005934; Fri, 27 Jul 2012 12:12:38 -0400 (EDT) From: Tom Lane To: Alanoly Andrews cc: "'pgsql-admin@postgresql.org'" Subject: Re: pg_dump on Postgres 9.1 In-reply-to: <09B23E7BF70425478C1330D893A722C606F6088EE5@MailSVR.invera.com> References: <09B23E7BF70425478C1330D893A722C606F6088EE5@MailSVR.invera.com> Comments: In-reply-to Alanoly Andrews message dated "Fri, 27 Jul 2012 11:49:44 -0400" Date: Fri, 27 Jul 2012 12:12:38 -0400 Message-ID: <5933.1343405558@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/98 X-Sequence-Number: 39815 Alanoly Andrews writes: > Is there any reported bug with pg_dump in Postgres 9.1, on AIX ? The following command hangs for "ever" and has to be interrupted. It creates a zero-length file. We had a recent report of strange server-side behavior on AIX that went away after rebuilding with a newer version of xlc, suggesting that the code was getting bitten by an xlc optimization bug. Perhaps this is the same thing inside pg_dump. If you're not using the latest xlc, try updating. If you are, does rebuilding with -O0 change the behavior? regards, tom lane