[copying the list; please keep the list copied on all replies]
Ramana Panda wrote:
> I am using the Version : *"PostgreSQL 8.0.0 on i686-pc-mingw32,
> compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)"*
You didn't even keep up on bug fix releases? It's amazing that your
database is still r
"ramana.pls" wrote:
> I am getting an error while restoring the Database Backup. I am
> postgre sql 8.0 with Windows XP O.S.
PostgreSQL version 8.0 has been out of support overall for years,
and out of support for Windows for years before that.
http://archives.postgresql.org/pgsql-announce/2
"ramana.pls" writes:
> I am getting an error while restoring the Database Backup. I am postgre sql
> 8.0 with Windows XP O.S.
8.0? You do know that's been out of support for several years now,
right?
> while restoring the data i am getting
> pg_restore: [custom archiver] found unexpected block
Hi ,
I am getting an error while restoring the Database Backup. I am postgre sql
8.0 with Windows XP O.S.
while restoring the data i am getting
pg_restore: [custom archiver] found unexpected block ID (0) when reading
data --
expected 4034
Plz provide any solution.
Thanks in advance
--
Vi
Hi ALL,
I am trying to restore 2G dump file using pg_restore and it will erros
out with the following message;
pg_restore: [custom archiver] could not uncompress data: too many length
or distance symbol". Has anyone seen this before? I 'd really appreciate
your help.
Thanks,
Dinesh
--
mailto:[EMAIL PROTECTED] Behalf Of David Olbersen
> Sent: Tuesday, July 22, 2003 4:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [ADMIN] pg_restore problem!!!
>
>
> Nick,
>
> > pg_dump dbname | gzip > dbdumpfile.gz
> >
> > gunzip -c dbdumpfile | psql dbname
Diego, CA 92127
1-858-676-2277 x2152
> -Original Message-
> From: Nick Fankhauser [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 22, 2003 2:05 PM
> To: David Olbersen; [EMAIL PROTECTED]
> Subject: RE: [ADMIN] pg_restore problem!!!
>
>
>
> > To nit-pick,
> To nit-pick, this is a "useless use of cat".
>
> In UNIX-land, simple input redirection will work much better:
>
> psql [dbname and various options] < [filename]
Good point... to elaborate further, the reason I was in a piping mindset is
that with a large database, it also makes sense to comp
Thank you.
You saved my day!!!
That command restores all my data into my DB.
MAGO
---Mensaje original---
De: David Olbersen
Fecha: Martes, 22 de Julio de 2003 03:02:48 p.m.
A: [EMAIL PROTECTED]
Asunto: Re: [ADMIN] pg_restore problem!!!
Nick,> To restore from a plain-text d
2152
> -Original Message-
> From: Nick Fankhauser [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 22, 2003 1:30 PM
> To: Marvin; [EMAIL PROTECTED]
> Subject: Re: [ADMIN] pg_restore problem!!!
>
>
> Mago-
>
> pg_restore is used to restore a dump file created in
]
Subject: [ADMIN] pg_restore problem!!!
I made a back up file with this sentence:
pg_dump -U [superusername] -C -D -f [filename] [dbname]
It seems to work fine. I opened the file and I saw all the commands to
insert every piece of data and reconstruct my schema. However when I try to
restore that file
I made a back up file with this sentence:
pg_dump -U [superusername] -C -D -f [filename] [dbname]
It seems to work fine. I opened the file and I saw all the commands to insert every piece of data and reconstruct my schema. However when I try to restore that file it gets me the following
> $pg_restore -a -d DB2 -Fc -o -v DB1.dump
As I'm running pg_restore like this and is taking to long,
is there any other way to restore OIDs/lo objects?
TIA
Ricardo
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregis
> Are you sure your restoring to an empty database? If you try to restore
> your dump into the database you dumped it from (without first
> drop/create) it will take forever as you'll have all kinds of data
> collisions (imagine every insert into a table erroring out due to
> duplicate primary key)
Did this ever get addressed?
---
Tom Lane wrote:
> Ian Burrell <[EMAIL PROTECTED]> writes:
> > I just recreated the problem with a slightly different command. The
> > problem was caused by using a list file to skip loading
Not receiving any admin messages as of now...this message is for
troubleshooting only. Please ignore.
--
Kevin Brown [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, p
Ian Burrell <[EMAIL PROTECTED]> writes:
> I just recreated the problem with a slightly different command. The
> problem was caused by using a list file to skip loading some function
> definitions that were causing problems. The command that loaded
> everything into template1 was:
> pg_restore
Tom Lane wrote:
I tried to replicate this, and could not: the restore went into the
expected database. (But I did notice that pg_restore needed to be
explicitly told -Ft, which seems less than bright of it.) Are you
sure those are the exact commands you issued? Were you using the 7.3
versions
Ian Burrell <[EMAIL PROTECTED]> writes:
> ...and used tar format backup: "pg_dump -Ft -b mpmx > backup.tar".
> pg_restore -C -d template1 backup.tar
> Instead of creating the mpmx database, the command loaded everything
> into the template1 database.
I tried to replicate this, and could not: the
On Fri, 31 Jan 2003, Ian Burrell wrote:
> How can I return template1 to its initial state?
>
> - Ian
>
I know how to return template1 to its initial state.
http://techdocs.postgresql.org/techdocs/pgsqladventuresep1.php
Sorry, I can't help with your other questions.
Good luck!
--
Jeff Ross
Op
I am upgrading my PostgreSQL install from 7.2.3 to 7.3.1. I ran into a
problem with pg_restore creating the database. I am not sure if this is
a documentation problem or a real bug. I have one database with BLOBs
and used tar format backup: "pg_dump -Ft -b mpmx > backup.tar".
I saw the -C op
I got this error message:
pg_restore: [archiver] input file does not appear to be a valid archive
after the command:
pg_restore -d mydb_name mydb_name.dump.tar
the tar file was created with the command
pg_dump -b -f mydb_name.dump.tar -F t mydb_name
==
This is exactly what is said in the Man
hi,
Before taking backup with pg_dump, give createdb and createuser
privileges to all the users of the first database.Then restore it
in the second database with pg_restore.I don't know why they made
the privileges required for taking backup.
--with regrard
chava
--
Srinivasa R Chava (Chava) <[E
I'm trying to backup and restore database from DBname to DBname2 (e.g. copy
database. it is for example).
When i'm trying to use these commands :
#pg_dump -f DBname.tar -b -o -Ft DBname
#createdb DBname2
#pg_restore -Ft -d DBname2 -f DBname.tar
pg_dump works fine, but pg_restore produce thi
24 matches
Mail list logo
