pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_restore problem.
17+ messages / 11 participants
[nested] [flat]
* pg_restore problem.
@ 2002-03-04 05:44 Alex Hudich <altx@mail.ru>
0 siblings, 1 reply; 17+ messages in thread
From: Alex Hudich @ 2002-03-04 05:44 UTC (permalink / raw)
To: pgsql-admin
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 this error message :
Archiver(db): Could not execute query. No result from backend.
What's wrong?
Help me, please.
---
cul8er!
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem.
@ 2002-03-07 17:21 Srinivasa R Chava <s.chava@wcom.com>
parent: Alex Hudich <altx@mail.ru>
0 siblings, 0 replies; 17+ messages in thread
From: Srinivasa R Chava @ 2002-03-07 17:21 UTC (permalink / raw)
To: Alex Hudich <altx@mail.ru>; +Cc: pgsql-admin
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) <s.chava@wcom.com>
- Boss: Sean T Laduderdale <sean.lauderdale@wcom.com>
vnet4603575
Application Developer
Corporate Intra/Internet Systems
WORLDCOM - http://www.worldcom.com/ - NASDAQ:WCOM
500 Clinton Center Drive (Corporate Headquarters)
Clinton, Mississippi (MS) USA 39056
(601)460-3122 / vnet4603122 / (800)844-1009 / FAX(601)460-8257
^ permalink raw reply [nested|flat] 17+ messages in thread
* pg_restore problem
@ 2003-01-17 02:17 Kemin Zhou <kemin.zhou@ferring.com>
0 siblings, 0 replies; 17+ messages in thread
From: Kemin Zhou @ 2003-01-17 02:17 UTC (permalink / raw)
To: pgsql-admin
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 pages in pg_dump and pg_restore.
I am using postgres 7.3.1
My question: Is this a bug in the new release? Or I am totally stupid.
Help would be appreciated.
Kemin
^ permalink raw reply [nested|flat] 17+ messages in thread
* pg_restore problem
@ 2003-03-28 12:35 lists <lists@insyde.com.br>
0 siblings, 1 reply; 17+ messages in thread
From: lists @ 2003-03-28 12:35 UTC (permalink / raw)
To: pgsql-admin
Hi,
I've a dump I made with the command:
pg_dump -a -b -Fc -f DB.dump -o -v DB
then I try to restore with:
pg_restore -a -d DB2 -Fc -o -v DB.dump
This database is about 1.5Gb big.
The dump takes abou 1 hour, but the restore takes forever!
Last time I ran it, it takes more than 10 hours, when I gave up
and stopped the process.
Tried with both Ft and Fc.
Another doubt: Why a dump of this DB with Ft has about the
same size of the original DB(1.5GB) and with Fc it has about 50MB?
My system is:
P3 1Ghz, 1GB ram, Win2k, Postgres 7.2.2
Free space ~5GB.
TIA,
Ricardo.
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem
@ 2003-03-31 13:43 Robert Treat <xzilla@users.sourceforge.net>
parent: lists <lists@insyde.com.br>
0 siblings, 1 reply; 17+ messages in thread
From: Robert Treat @ 2003-03-31 13:43 UTC (permalink / raw)
To: lists <lists@insyde.com.br>; +Cc: pgsql-admin
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).
As for the -Ft vs. -Fc size question, the tar format is not a compressed
format, while the "c"ustom format is.
Robert Treat
On Fri, 2003-03-28 at 07:35, lists wrote:
> Hi,
>
> I've a dump I made with the command:
>
> pg_dump -a -b -Fc -f DB.dump -o -v DB
>
> then I try to restore with:
>
> pg_restore -a -d DB2 -Fc -o -v DB.dump
>
> This database is about 1.5Gb big.
>
> The dump takes abou 1 hour, but the restore takes forever!
>
> Last time I ran it, it takes more than 10 hours, when I gave up
> and stopped the process.
>
> Tried with both Ft and Fc.
>
> Another doubt: Why a dump of this DB with Ft has about the
> same size of the original DB(1.5GB) and with Fc it has about 50MB?
>
> My system is:
> P3 1Ghz, 1GB ram, Win2k, Postgres 7.2.2
> Free space ~5GB.
>
> TIA,
>
> Ricardo.
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem
@ 2003-03-31 14:19 lists <lists@insyde.com.br>
parent: Robert Treat <xzilla@users.sourceforge.net>
0 siblings, 1 reply; 17+ messages in thread
From: lists @ 2003-03-31 14:19 UTC (permalink / raw)
To: pgsql-admin
> 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).
Yes, I'm sure it is an empty database. I didn't mention in the e-mail,
but the complete script I did is:
$pg_dump -s DB1 > DB1.sql
$pg_dump -a -b -Fc -f DB1.dump -o -v DB1
$dropdb DB2
$createdb DB2
$psql DB2 <DB1.sql
$pg_restore -a -d DB2 -Fc -o -v DB1.dump
So it's a brand new DB I'm restoring to.
> As for the -Ft vs. -Fc size question, the tar format is not a compressed
> format, while the "c"ustom format is.
Thanks.
Ricardo.
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem
@ 2003-04-01 14:28 lists <lists@insyde.com.br>
parent: lists <lists@insyde.com.br>
0 siblings, 0 replies; 17+ messages in thread
From: lists @ 2003-04-01 14:28 UTC (permalink / raw)
To: pgsql-admin
> $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
^ permalink raw reply [nested|flat] 17+ messages in thread
* pg_restore problem!!!
@ 2003-07-22 20:21 Marvin <magosoft@gmx.net>
0 siblings, 1 reply; 17+ messages in thread
From: Marvin @ 2003-07-22 20:21 UTC (permalink / raw)
To: pgsql-admin
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 error:
C:\>pg_restore [filename]
pg_restore: [archiver] input file does not appear to be a valid archive
What I am doing wrong??
Any ideas??
Thank you in advanced.
MAGO
Attachments:
IMSTP.gif (image/gif, 494B) download
view image
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem!!!
@ 2003-07-22 20:29 Nick Fankhauser <nickf@ontko.com>
parent: Marvin <magosoft@gmx.net>
0 siblings, 0 replies; 17+ messages in thread
From: Nick Fankhauser @ 2003-07-22 20:29 UTC (permalink / raw)
To: Marvin <magosoft@gmx.net>; pgsql-admin
Mago-
pg_restore is used to restore a dump file created in one of the non-text
formats such as tar format.
To restore from a plain-text dump file, just pipe it into psql like so:
cat [filename] | psql [dbname]
-Nick
---------------------------------------------------------------------
Nick Fankhauser
nickf@doxpop.com Phone 1.765.965.7363 Fax 1.765.962.9788
doxpop - Court records at your fingertips - http://www.doxpop.com/
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Marvin
Sent: Tuesday, July 22, 2003 3:22 PM
To: pgsql-admin@postgresql.org
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 it gets me the following error:
C:\>pg_restore [filename]
pg_restore: [archiver] input file does not appear to be a valid archive
What I am doing wrong??
Any ideas??
Thank you in advanced.
MAGO
_________________________________________________________________
IncrediMail - El E-mail ha evolucionado finalmente - Haga clic aquí
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem!!!
@ 2003-07-22 20:54 David Olbersen <DOlbersen@stbernard.com>
0 siblings, 2 replies; 17+ messages in thread
From: David Olbersen @ 2003-07-22 20:54 UTC (permalink / raw)
To: pgsql-admin
Nick,
> To restore from a plain-text dump file, just pipe it into
> psql like so:
>
> cat [filename] | psql [dbname]
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]
It's also less to type! :)
I also believe this works in certain Windows operating systems, which is what it appears Mago is using.
--------------------------
David Olbersen
iGuard Engineer
St. Bernard Software
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152
> -----Original Message-----
> From: Nick Fankhauser [mailto:nickf@ontko.com]
> Sent: Tuesday, July 22, 2003 1:30 PM
> To: Marvin; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_restore problem!!!
>
>
> Mago-
>
> pg_restore is used to restore a dump file created in one of
> the non-text
> formats such as tar format.
>
> To restore from a plain-text dump file, just pipe it into
> psql like so:
>
> cat [filename] | psql [dbname]
>
> -Nick
>
> ---------------------------------------------------------------------
> Nick Fankhauser
>
> nickf@doxpop.com Phone 1.765.965.7363 Fax 1.765.962.9788
> doxpop - Court records at your fingertips - http://www.doxpop.com/
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org
> [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Marvin
> Sent: Tuesday, July 22, 2003 3:22 PM
> To: pgsql-admin@postgresql.org
> 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 it gets me the following error:
>
> C:\>pg_restore [filename]
> pg_restore: [archiver] input file does not appear to be a
> valid archive
>
> What I am doing wrong??
> Any ideas??
>
> Thank you in advanced.
>
>
> MAGO
>
>
> _________________________________________________________________
> IncrediMail - El E-mail ha evolucionado finalmente - Haga clic aquí
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 8: explain analyze is your friend
>
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem!!!
@ 2003-07-22 21:04 Nick Fankhauser <nickf@ontko.com>
parent: David Olbersen <DOlbersen@stbernard.com>
1 sibling, 0 replies; 17+ messages in thread
From: Nick Fankhauser @ 2003-07-22 21:04 UTC (permalink / raw)
To: David Olbersen <DOlbersen@stbernard.com>; pgsql-admin
> 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 compress on the fly to
avoid filesystem size limits, so I usually use this pair of commands for
backup/restore:
pg_dump dbname | gzip > dbdumpfile.gz
gunzip -c dbdumpfile | psql dbname
-Nick
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem!!!
@ 2003-07-22 21:08 Marvin <magosoft@gmx.net>
parent: David Olbersen <DOlbersen@stbernard.com>
1 sibling, 0 replies; 17+ messages in thread
From: Marvin @ 2003-07-22 21:08 UTC (permalink / raw)
To: DOlbersen@stbernard.com; +Cc: pgsql-admin
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: pgsql-admin@postgresql.org
Asunto: Re: [ADMIN] pg_restore problem!!!
Nick,
> To restore from a plain-text dump file, just pipe it into
> psql like so:
>
> cat [filename] | psql [dbname]
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]
It's also less to type! :)
I also believe this works in certain Windows operating systems, which is
what it appears Mago is using.
--------------------------
David Olbersen
iGuard Engineer
St. Bernard Software
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152
> -----Original Message-----
> From: Nick Fankhauser [mailto:nickf@ontko.com]
> Sent: Tuesday, July 22, 2003 1:30 PM
> To: Marvin; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_restore problem!!!
>
>
> Mago-
>
> pg_restore is used to restore a dump file created in one of
> the non-text
> formats such as tar format.
>
> To restore from a plain-text dump file, just pipe it into
> psql like so:
>
> cat [filename] | psql [dbname]
>
> -Nick
>
> ---------------------------------------------------------------------
> Nick Fankhauser
>
> nickf@doxpop.com Phone 1.765.965.7363 Fax 1.765.962.9788
> doxpop - Court records at your fingertips - http://www.doxpop.com/
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org
> [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Marvin
> Sent: Tuesday, July 22, 2003 3:22 PM
> To: pgsql-admin@postgresql.org
> 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 it gets me the following error:
>
> C:\>pg_restore [filename]
> pg_restore: [archiver] input file does not appear to be a
> valid archive
>
> What I am doing wrong??
> Any ideas??
>
> Thank you in advanced.
>
>
> MAGO
>
>
> _________________________________________________________________
> IncrediMail - El E-mail ha evolucionado finalmente - Haga clic aquí
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 8: explain analyze is your friend
>
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
.
Attachments:
IMSTP.gif (image/gif, 494B) download
view image
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem!!!
@ 2003-07-22 21:15 David Olbersen <DOlbersen@stbernard.com>
0 siblings, 1 reply; 17+ messages in thread
From: David Olbersen @ 2003-07-22 21:15 UTC (permalink / raw)
To: pgsql-admin
Nick,
> pg_dump dbname | gzip > dbdumpfile.gz
>
> gunzip -c dbdumpfile | psql dbname
If you're compressing why not use:
pg_dump -Fc dbname -f dbdumpfile
pg_restore dbdumpfile
?
Don't take this the wrong way, I'm genuinely curious! When I first started I didn't realize we did our dumps this way and tried to gzip one of the dump files: and got 0% savings!
If this is a way to reduce the size of my nightly dumps I'm all for it! :)
--------------------------
David Olbersen
iGuard Engineer
St. Bernard Software
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152
> -----Original Message-----
> From: Nick Fankhauser [mailto:nickf@ontko.com]
> Sent: Tuesday, July 22, 2003 2:05 PM
> To: David Olbersen; pgsql-admin@postgresql.org
> Subject: RE: [ADMIN] pg_restore problem!!!
>
>
>
> > 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 compress
> on the fly to
> avoid filesystem size limits, so I usually use this pair of
> commands for
> backup/restore:
>
> pg_dump dbname | gzip > dbdumpfile.gz
>
> gunzip -c dbdumpfile | psql dbname
>
> -Nick
>
>
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: pg_restore problem!!!
@ 2003-07-22 22:02 Nick Fankhauser <nickf@ontko.com>
parent: David Olbersen <DOlbersen@stbernard.com>
0 siblings, 0 replies; 17+ messages in thread
From: Nick Fankhauser @ 2003-07-22 22:02 UTC (permalink / raw)
To: David Olbersen <DOlbersen@stbernard.com>; pgsql-admin
Hi David-
I don't use the -Fc or -Ft format exclusively because I ran into dependency
problems with the order of object creation when trying to do a full
database restore using pg_restore and these formats.
Since we have a fair amount of space, I do both a tar format and a
plain-text format dump every night. This gives me the option of quickly
restoring the entire database from the plain text version (which has no
dependency problems), but then also easily restoring a single object or
group of objects using pg_restore from the tar format. I haven't explored
using the c (custom/compressed) format because when I inquired about the
dependency problems I encountered with the tar format, I learned that this
was a known problem in every format except plain text.
If you're using only -Fc format, you might want to try running a full
restore to make sure you don't have to reorder elements during recovery. I
opted to do both formats because our database is subject to regular
structure changes, so I can't tell how elements will have to be re-ordered
in advance. I like all of my restore pre-plans to be simple enough to
execute quickly and with little thought while many people are talking to me.
(Because it is well-known among most users that distracting your SysAdmin
with frequent visits and phone calls makes him work faster and ensures that
your system gets restored more quickly.)
-NF
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org
> [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of David Olbersen
> Sent: Tuesday, July 22, 2003 4:15 PM
> To: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] pg_restore problem!!!
>
>
> Nick,
>
> > pg_dump dbname | gzip > dbdumpfile.gz
> >
> > gunzip -c dbdumpfile | psql dbname
>
> If you're compressing why not use:
>
> pg_dump -Fc dbname -f dbdumpfile
> pg_restore dbdumpfile
>
> ?
>
> Don't take this the wrong way, I'm genuinely curious! When I
> first started I didn't realize we did our dumps this way and
> tried to gzip one of the dump files: and got 0% savings!
>
> If this is a way to reduce the size of my nightly dumps I'm all for it! :)
>
> --------------------------
> David Olbersen
> iGuard Engineer
> St. Bernard Software
> 11415 West Bernardo Court
> San Diego, CA 92127
> 1-858-676-2277 x2152
>
>
> > -----Original Message-----
> > From: Nick Fankhauser [mailto:nickf@ontko.com]
> > Sent: Tuesday, July 22, 2003 2:05 PM
> > To: David Olbersen; pgsql-admin@postgresql.org
> > Subject: RE: [ADMIN] pg_restore problem!!!
> >
> >
> >
> > > 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 compress
> > on the fly to
> > avoid filesystem size limits, so I usually use this pair of
> > commands for
> > backup/restore:
> >
> > pg_dump dbname | gzip > dbdumpfile.gz
> >
> > gunzip -c dbdumpfile | psql dbname
> >
> > -Nick
> >
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
^ permalink raw reply [nested|flat] 17+ messages in thread
* PG restore problem
@ 2004-01-08 06:26 vidhya <vidhya@ellaar.com>
0 siblings, 1 reply; 17+ messages in thread
From: vidhya @ 2004-01-08 06:26 UTC (permalink / raw)
To: pgsql-admin
HI,
I am using postgresql 7.3.3 in win2k.
When we restore the database, the following error occurs and the Postgres crashes immediately.
LOG: ReadRecord: unexpected pageaddr 0/FC1E6000 in log file 1, segment 5,
offset 1990656
Pls tell me a solution to overcome this problem (urgent).
Regards,
Vidhya.
^ permalink raw reply [nested|flat] 17+ messages in thread
* Re: PG restore problem
@ 2004-01-08 14:38 Tom Lane <tgl@sss.pgh.pa.us>
parent: vidhya <vidhya@ellaar.com>
0 siblings, 0 replies; 17+ messages in thread
From: Tom Lane @ 2004-01-08 14:38 UTC (permalink / raw)
To: vidhya <vidhya@ellaar.com>; +Cc: pgsql-admin
"vidhya" <vidhya@ellaar.com> writes:
> I am using postgresql 7.3.3 in win2k.
> When we restore the database, the following error occurs and the Postgres c=
> rashes immediately.
> LOG: ReadRecord: unexpected pageaddr 0/FC1E6000 in log file 1, segment 5,
> offset 1990656
Update to 7.3.4 or 7.3.5. This is the 7.3.3 startup-failure-at-page-boundary
problem.
regards, tom lane
^ permalink raw reply [nested|flat] 17+ messages in thread
* pg_restore problem
@ 2007-11-29 01:05 Dinesh <dbhandary@mongonet.net>
0 siblings, 0 replies; 17+ messages in thread
From: Dinesh @ 2007-11-29 01:05 UTC (permalink / raw)
To: pgsql-admin
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
^ permalink raw reply [nested|flat] 17+ messages in thread
end of thread, other threads:[~2007-11-29 01:05 UTC | newest]
Thread overview: 17+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-03-04 05:44 pg_restore problem. Alex Hudich <altx@mail.ru>
2002-03-07 17:21 ` Srinivasa R Chava <s.chava@wcom.com>
2003-01-17 02:17 pg_restore problem Kemin Zhou <kemin.zhou@ferring.com>
2003-03-28 12:35 pg_restore problem lists <lists@insyde.com.br>
2003-03-31 13:43 ` Re: pg_restore problem Robert Treat <xzilla@users.sourceforge.net>
2003-03-31 14:19 ` Re: pg_restore problem lists <lists@insyde.com.br>
2003-04-01 14:28 ` Re: pg_restore problem lists <lists@insyde.com.br>
2003-07-22 20:21 pg_restore problem!!! Marvin <magosoft@gmx.net>
2003-07-22 20:29 ` Re: pg_restore problem!!! Nick Fankhauser <nickf@ontko.com>
2003-07-22 20:54 Re: pg_restore problem!!! David Olbersen <DOlbersen@stbernard.com>
2003-07-22 21:04 ` Re: pg_restore problem!!! Nick Fankhauser <nickf@ontko.com>
2003-07-22 21:08 ` Re: pg_restore problem!!! Marvin <magosoft@gmx.net>
2003-07-22 21:15 Re: pg_restore problem!!! David Olbersen <DOlbersen@stbernard.com>
2003-07-22 22:02 ` Re: pg_restore problem!!! Nick Fankhauser <nickf@ontko.com>
2004-01-08 06:26 PG restore problem vidhya <vidhya@ellaar.com>
2004-01-08 14:38 ` Re: PG restore problem Tom Lane <tgl@sss.pgh.pa.us>
2007-11-29 01:05 pg_restore problem Dinesh <dbhandary@mongonet.net>
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