No, the file needs to be nothing but hex value 55 throughout. The
attachment I sent earlier is just that:
[EMAIL PROTECTED]:~$ hexdump 55
000
*
004
i.e. all 55s, all the time, not the ascii numbers 5 and 5, but the hex
value. The actual file is as
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 <[EMAIL PROTECTED]> writes:
Are the files that contain the hex characters supposed to contain a
single string and no control characters?
Yes, you want 256K o
Carol Walter <[EMAIL PROTECTED]> writes:
> Here is the results of the query you asked for.
> datname | datfrozenxid
> --+--
> postgres | 524
> ...
Huh. Postgres should never have removed any of those files with
datfrozenxid this low. S
Carol Walter <[EMAIL PROTECTED]> 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
Hi, Tom,
Are the files that contain the hex characters supposed to contain a
single string and no control characters? I used Excel to create the
files, but I'll have to edit them when I get them to the Solaris box
to take out any bad characters.
I'm also wondering if, after I create the
Yes, as an experienced dba, there ist no excuse for not having the
routine backups. I do it for the other instances but not this one.
It's student contains student databases. The students are required
to do there own backups. The problem is, the database got used for
some non-student da
Carol Walter <[EMAIL PROTECTED]> writes:
> I tried creating the files through 002F. Pg_dump still will not
> run. The error was as follows:
> -bash-3.00$ pg_dump -U postgres ebiz > ebiz_bk.sql
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: could not access sta
Hello,
I tried creating the files through 002F. Pg_dump still will not
run. The error was as follows:
-bash-3.00$ pg_dump -U postgres ebiz > ebiz_bk.sql
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: could not access status
of transaction 20080015
DETAIL: Co
Hello,
I will try this. Is there a particular size these files need to be?
Then I can try the pg_dumpall. That's, of course, my main concern. I
need to get the data out.
By the way, before I went to panic mode, I tried pg_dumpall and
reindexing the database. Everything gets the same err
Carol Walter; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Missing pg_clog files
On Tue, Sep 23, 2008 at 10:16 PM, Tena Sakai <[EMAIL PROTECTED]> wrote:
> Hi Carol,
>
> I detect in you some apprehension as to pg_dumpall
> won't run or complete. Why is that? Have yo
On Tue, Sep 23, 2008 at 10:16 PM, Tena Sakai <[EMAIL PROTECTED]> wrote:
> Hi Carol,
>
> I detect in you some apprehension as to pg_dumpall
> won't run or complete. Why is that? Have you already
> done it and it didn't work? If that's not the case,
> why not run pg_dumpall at a quiet hour and see
TECTED] on behalf of Carol Walter
Sent: Tue 9/23/2008 8:35 PM
To: Scott Marlowe
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Missing pg_clog files
Hello,
Here are the pg_clog files I still have.
-rw--- 1 postgres postgres 262144 Jun 4 18:43 0030
-rw--- 1 postgres postgres
Hello,
Here are the pg_clog files I still have.
-rw--- 1 postgres postgres 262144 Jun 4 18:43 0030
-rw--- 1 postgres postgres 262144 Jun 6 02:06 0031
-rw--- 1 postgres postgres 262144 Jun 7 01:26 0032
-rw--- 1 postgres postgres 262144 Jun 7 21:26 0033
-rw---
On Tue, Sep 23, 2008 at 7:59 PM, Walter, Carol Williams
<[EMAIL PROTECTED]> wrote:
> Hi, Tena,
>
> I actually downloaded 8.3.3 last week. The upgrade has been in the plan. I
> didn't realize the latest was 8.3.4. I am concerned though. We have so many
> dependencies that they never go smoothly.
t: Tue 9/23/2008 4:56 PM
To: Carol Walter
Cc: Tena Sakai; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Missing pg_clog files
On Tue, Sep 23, 2008 at 4:35 PM, Carol Walter <[EMAIL PROTECTED]> wrote:
Hi, Tena,
Yes, you do recall correctly. It is Solaris 10 and Postgres 8.2.3.
I'm go
rlowe [mailto:[EMAIL PROTECTED]
Sent: Tue 9/23/2008 4:56 PM
To: Carol Walter
Cc: Tena Sakai; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Missing pg_clog files
On Tue, Sep 23, 2008 at 4:35 PM, Carol Walter <[EMAIL PROTECTED]> wrote:
> Hi, Tena,
> Yes, you do recall correctly. It
On Tue, Sep 23, 2008 at 4:35 PM, Carol Walter <[EMAIL PROTECTED]> wrote:
> Hi, Tena,
> Yes, you do recall correctly. It is Solaris 10 and Postgres 8.2.3.
> I'm going to run a pg_dumpall and keep my fingers crossed. I'm getting
> similar errors when I try to do other things like vacuumdb, so maybe
ECTED]
-Original Message-
From: [EMAIL PROTECTED] on behalf of Carol Walter
Sent: Tue 9/23/2008 2:31 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Missing pg_clog files
I'm missing about 30 pg_clog files. How do I recover from this?
Carol
--
Sent via pgsql-admin mailing list (
ssage-
From: [EMAIL PROTECTED] on behalf of Carol Walter
Sent: Tue 9/23/2008 2:31 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Missing pg_clog files
I'm missing about 30 pg_clog files. How do I recover from this?
Carol
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org
I'm missing about 30 pg_clog files. How do I recover from this?
Carol
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
20 matches
Mail list logo
