Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id C12AB9FA07D for ; Mon, 8 Oct 2007 14:11:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 69139-05 for ; Mon, 8 Oct 2007 14:11:43 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id 893909FA0D5 for ; Mon, 8 Oct 2007 14:11:42 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so874581ugf for ; Mon, 08 Oct 2007 10:11:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Y2u5Ri3JyZZ952TQpcV34WfZfYvdD0+muCaU2tFm39g=; b=UKJVCFwwQNkxySv3L27gQXLlg6dTQtY+ZcTWCCwaOQtvvUQgYCDc6+DwO/CCEiC7f+OTS9kSV/hKWVuonRxqsaPtpHV8uucsfdd3cbNlt9mYqf5LnQLnDShXx/fU9IzySlXRn4HCLg6Y6+PZ9KGtMC8L2t1V+IkgjZFB6FxJ3Kc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HP9dKHmQQiIjdsUftQJ8zj48LiJKn67fhXFl4B/lTVP67fKyD8EXtSXeHj0UoMkZtqCAeZQF3v9XfDNlzONo6AWs8qv6TNHvSwUkmuMwSDd/GFnm80taNpMwirMt+HEl/akLBv9HhqIQI2eA8XBYaUut+DXunPFSPBoL75f/mbs= Received: by 10.66.218.15 with SMTP id q15mr7030143ugg.1191863500580; Mon, 08 Oct 2007 10:11:40 -0700 (PDT) Received: by 10.66.220.7 with HTTP; Mon, 8 Oct 2007 10:11:40 -0700 (PDT) Message-ID: Date: Mon, 8 Oct 2007 12:11:40 -0500 From: "Scott Marlowe" To: "Darren Reed" Subject: Re: postgres: will not recognise existing tables Cc: pgsql-admin@postgresql.org In-Reply-To: <47084A40.3020807@fastmail.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47084A40.3020807@fastmail.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/55 X-Sequence-Number: 26969 On 10/6/07, Darren Reed wrote: > I've run into this problem twice in the last few days. > > postgresql is running, shutdown, reboot, restart, and tables are missing. > > The shutdown is clean: > LOG: unexpected EOF on client connection > LOG: received smart shutdown request > LOG: shutting down > LOG: database system is shut down > LOG: database system was shut down at 2007-10-06 18:50:33 PDT > LOG: checkpoint record is at 2/3310F20C > LOG: redo record is at 2/3310F20C; undo record is at 0/0; shutdown TRUE > LOG: next transaction ID: 228741; next OID: 16449 > LOG: next MultiXactId: 1; next MultiXactOffset: 0 > LOG: database system is ready > LOG: transaction ID wrap limit is 2147484146, limited by database > "postgres" > LOG: received smart shutdown request > LOG: shutting down > LOG: database system is shut down > > The startup is clean: > FATAL: lock file "postmaster.pid" already exists > HINT: Is another postmaster (PID 99) running in data directory > "/home/postgres/ > db"? That's not a clean startup. The postmaster.pid should not exist. Are sure you are not running postgresql in > 1 location on this machine... Do you have an exact copy of a session where you see this happen? I.e. the pg_ctl start, table updates, pg_ctl stop, pg_ctl start, table corrupted? Including log files... I feel like we're kind of dancing around the problem in the dark without enough info. Please note this is absolutely non-normal behaviour. I've been using pgsql since v6.5.2 and never had this occur to me. As for your ulimit settings, what are they, specifically for the postgres account on this machine, both explicit and inherited?