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
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:
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 status
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
Hi Peter,
On Tue, 2008-09-23 at 23:09 +0300, Peter Eisentraut wrote:
SLES builds have been broken for a while. I have not analyzed that
yet.
Bugs and patches welcome.
https://projects.commandprompt.com/public/pgcore/repo/rpm/suse/8.3/SLES-10/postgresql.spec
(it is using self-signed cert,
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
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
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. So it
Is there any ways to include wildcard in pg_hba.conf file to accept all
postgres clients on the network rather than specifying specific IP addresses on
this file?
Any assistance is appreciated
Thanks
Napolean
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make
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
Napolean Periathambi [EMAIL PROTECTED] wrote:
Is there any ways to include wildcard in pg_hba.conf file to accept
all
postgres clients on the network rather than specifying specific IP
addresses
on this file?
# CIDR-ADDRESS specifies the set of hosts the record matches.
# It is made up
Our database seems to have been corrupted. It is a heavily used database,
and went several months without any type of vacuuming. When we finally
realized that it wasn't being vacuumed, we started the process, but the
process never successfully completed, and our database has never been the
same
Hello,
Does anyone know what the format of hex characters for postgres are?
I'm trying to create files that contain a 0x55. It looks to me like
it should require a delimiter of some sort between the characters. I
don't know how postgres would know that the string was a hex
I ran into this issue awhile ago. Here's my long internal tech note to my
dev guys on what I did. A bit modified for more genericism:
I'm in the process of migrating our internal db server, and I decided to use
the helpdesk as
my test database. It backed up fine last night. Something went
Testing AutoVac on 8.3 , i came across the problem of loosing stats data,
which was discussed in my last post
http://archives.postgresql.org/pgsql-general/2008-08/msg00198.php
that problem was recognized that doing hard stop, server will throw away the
stats while going through crash recovery.
Carol Walter написа:
Hello,
Does anyone know what the format of hex characters for postgres are?
I'm trying to create files that contain a 0x55. It looks to me like it
should require a delimiter of some sort between the characters. I don't
know how postgres would know that the string was
I used this very simple little php script to make this
filename: mk55:
#!/usr/bin/php -q
?php
for ($i=0;$i262144;$i++){
print chr(85);
}
?
and ran it:
./mk55 55
ls -l 55
-rw-r--r-- 1 smarlowe smarlowe 262144 2008-09-24 13:41 55
i.e. it's 256k.
And it's attached.
On Wed, Sep 24, 2008 at
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
BJ Taylor [EMAIL PROTECTED] writes:
Our database seems to have been corrupted. It is a heavily used database,
and went several months without any type of vacuuming. When we finally
realized that it wasn't being vacuumed, we started the process, but the
process never successfully completed,
Hello,
I'm not quite out of the woods yet, but I think I'm close. Here's
what I've done. There were some databases that were not effected by
the loss of the pg_clog files. I created a script than ran pg_dump
on each database while the files were missing. Then I created the
files that
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Hi Everybody,
I am sorry if this is an inappropriate way of finding out the
information, but I suspect that there is a bug in postgres on windows, I
tried searching for a similar bug on the net but only found
[EMAIL PROTECTED] to report bugs, before I send it as a
potential bug I would like to
22 matches
Mail list logo
