Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 1D40164FC24 for ; Wed, 24 Sep 2008 17:19:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 01078-06 for ; Wed, 24 Sep 2008 17:19:29 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.155]) by postgresql.org (Postfix) with ESMTP id 3EDCE64FC1E for ; Wed, 24 Sep 2008 17:19:29 -0300 (ADT) Received: by po-out-1718.google.com with SMTP id y22so58712pof.3 for ; Wed, 24 Sep 2008 13:19:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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=JF+7G594gbQMK1VIacilqdgyhhPlVy5XK2SeHe862OQ=; b=TVyIEsA0NqGkY06hiVxpU20mAgJx7kqE06S0kh3fzSWE/6XQt5eGbVbyQp6KGwNKEY hdhsLIvSy1rceBTB7Sov6NsHqrmVsKGiR1eSBCMqEA8Ki5viTmUbdAAfrKqmGzJvpFew dDajGl1JGsiTxjiSXCPp7PaK8x/aSqtV8y+lI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XrQW1RlYiS4QFsn7o/Y5unhcl7bNaEZWCQwbL9Oi2A47vp+JKAZE6dnZQsiTiZJFSB koN4HkqwZfuuXC14F7ZMVM0o25NMDW1yyJGctaSH/mvE1Uj6/PJm0lKzJ92AcK31xs4s G/mMw77VSItsyRuJfE+OG7E26XrGmGHZRRXPw= Received: by 10.141.114.19 with SMTP id r19mr3687558rvm.295.1222287568136; Wed, 24 Sep 2008 13:19:28 -0700 (PDT) Received: by 10.141.74.11 with HTTP; Wed, 24 Sep 2008 13:19:28 -0700 (PDT) Message-ID: Date: Wed, 24 Sep 2008 14:19:28 -0600 From: "Scott Marlowe" To: "Carol Walter" Subject: Re: Missing pg_clog files Cc: "Tom Lane" , "Tena Sakai" , pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080924071308.8lficujqsck8w44w@webmail.iu.edu> <052D4170-A065-4DDB-9F9D-6318E42C23BA@indiana.edu> <29313.1222261821@sss.pgh.pa.us> <4913.1222271062@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/292 X-Sequence-Number: 30385 No, the file needs to be nothing but hex value 55 throughout. The attachment I sent earlier is just that: smarlowe@sawyer:~$ hexdump 55 0000000 5555 5555 5555 5555 5555 5555 5555 5555 * 0040000 i.e. all 55s, all the time, not the ascii numbers 5 and 5, but the hex value. The actual file is ascii the letter U over and over: smarlowe@sawyer:~$ head -c 100 55 UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU and so on. On Wed, Sep 24, 2008 at 12:09 PM, Carol Walter wrote: > To use the hex value 0x55, do I need to enclose it in single quotes? > > Carol > > On Sep 24, 2008, at 11:44 AM, Tom Lane wrote: > >> Carol Walter writes: >>> >>> Are the files that contain the hex characters supposed to contain a >>> single string and no control characters? >> >> Yes, you want 256K occurrences of the byte value 0x55 and nothing else. >> >>> I'm also wondering if, after I create the dummy files, and pg_dump >>> works, I could restore an old pg_dumpall file and then insert any >>> data that aren't there from the pg_dumps. >> >> It'd be a good idea to do as much cross-checking as you can, since >> it's highly probable that the dumped data will be at least partly wrong. >> >> No, I'm afraid updating to 8.2.latest won't get you out of this. >> It might possibly prevent a recurrence. >> >> regards, tom lane >> >> -- >> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-admin > >