pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Carol Walter <walterc@indiana.edu>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tena Sakai <tsakai@gallo.ucsf.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Missing pg_clog files
Date: Wed, 24 Sep 2008 14:19:28 -0600
Message-ID: <dcc563d10809241319r12d27397s6f241019e7f34d93@mail.gmail.com> (raw)
In-Reply-To: <BEF66DB1-CD86-413E-9794-3A87FE1C092C@indiana.edu>
References: <CA701605-BE56-416C-9034-789B20180281@indiana.edu>
	<E22168D9-DDAD-4EE0-8CB9-8CA79FB26721@indiana.edu>
	<FE44E0D7EAD2ED4BB2165071DB8E328C0378F512@egcrc-ex01.egcrc.org>
	<dcc563d10809232121y47e27c32u94effea9809e494d@mail.gmail.com>
	<20080924071308.8lficujqsck8w44w@webmail.iu.edu>
	<052D4170-A065-4DDB-9F9D-6318E42C23BA@indiana.edu>
	<29313.1222261821@sss.pgh.pa.us>
	<FE8FD34C-4516-425A-B7AD-1917F134320F@indiana.edu>
	<4913.1222271062@sss.pgh.pa.us>
	<BEF66DB1-CD86-413E-9794-3A87FE1C092C@indiana.edu>

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 <walterc@indiana.edu> 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 <walterc@indiana.edu> 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
>
>



view thread (20+ messages)

Message-ID: <dcc563d10809241319r12d27397s6f241019e7f34d93@mail.gmail.com>
Permalink:  ../dcc563d10809241319r12d27397s6f241019e7f34d93@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10809241319r12d27397s6f241019e7f34d93@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: scott.marlowe@gmail.com, walterc@indiana.edu, tgl@sss.pgh.pa.us, tsakai@gallo.ucsf.edu
  Subject: Re: Missing pg_clog files
  In-Reply-To: <dcc563d10809241319r12d27397s6f241019e7f34d93@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox