X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 204C8D8872 for ; Thu, 1 Sep 2005 16:11:35 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 96394-03 for ; Thu, 1 Sep 2005 19:11:30 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 26B02D85B3 for ; Thu, 1 Sep 2005 16:11:28 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j81JBT5l005471; Thu, 1 Sep 2005 15:11:29 -0400 (EDT) To: Bartosz Nowak Cc: pgsql-admin@postgresql.org Subject: Re: pg_dumpall problem - duplicated users In-reply-to: <431750D4.3050808@go2.pl> References: <431739CD.1030906@go2.pl> <4997.1125599176@sss.pgh.pa.us> <431750D4.3050808@go2.pl> Comments: In-reply-to Bartosz Nowak message dated "Thu, 01 Sep 2005 21:04:52 +0200" Date: Thu, 01 Sep 2005 15:11:28 -0400 Message-ID: <5470.1125601888@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200509/7 X-Sequence-Number: 18744 Bartosz Nowak writes: > Tom Lane napisał(a): >> You could manually delete either row, probably better to zap the second >> one: >> delete from pg_shadow where ctid = '(1,25)'; > Heh... i wish it was that easy - i tried it already :] When i delete the > 'second' postgres user (with passwd set) PG is acting like there is no > postgres account at all: > ... > And i cannot modify row of 'first' postgres user (without passwd set) > with or without 'second' present: > mw=> delete from pg_shadow where ctid = '(0,1)' ; > DELETE 0 Ugh. That's looking more like you have a transaction ID wraparound problem. How long has it been since pg_shadow was last vacuumed? You could try a "VACUUM FREEZE pg_shadow" and see if the rows act any more normally after that. (Better take a filesystem-level backup first, so you can get out of it if that makes things worse.) regards, tom lane