pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_dump problem
18+ messages / 11 participants
[nested] [flat]
* pg_dump problem
@ 2000-07-21 19:38 John Burski <jburski@autopartshq.com>
0 siblings, 1 reply; 18+ messages in thread
From: John Burski @ 2000-07-21 19:38 UTC (permalink / raw)
To: pgsql-admin; pgsql-novice@postgresql.org
I'm having a bit of trouble with the "pg_dump' command in PostgeSQL
7.0.2 (running on Red Hat 6.0).
When I issue the "pg_dump jcon" (jcon being the database name, of
course) I receive the following error message:
getInherits(): SELECT failed
I'm issuing the command as the postgres "root" user - postgres - and I
have no problem accessing and manipulating the data in the "jcon"
database as that user.
Any help would be appreciated.
Thanks.
--
John R. Burski - (Title depends on the hat I'm wearing)
Automotive Parts Headquarters, Inc.
125 South 29th Avenue
Saint Cloud, MN 56301
320 252 5411 x137
Attachments:
smime.p7s (application/x-pkcs7-signature, 2.2K) download
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [NOVICE] pg_dump problem
@ 2000-07-21 22:05 Tom Lane <tgl@sss.pgh.pa.us>
parent: John Burski <jburski@autopartshq.com>
0 siblings, 1 reply; 18+ messages in thread
From: Tom Lane @ 2000-07-21 22:05 UTC (permalink / raw)
To: John Burski <jburski@autopartshq.com>; +Cc: pgsql-admin; pgsql-novice@postgresql.org
John Burski <jburski@autopartshq.com> writes:
> When I issue the "pg_dump jcon" (jcon being the database name, of
> course) I receive the following error message:
> getInherits(): SELECT failed
It might be time to put this in the FAQ ;-). You're probably trying
to run a 6.5 (or earlier?) pg_dump against a 7.0 database. The older
pg_dump doesn't do any version checking, and the first it realizes
it's got trouble is when it hits incompatibilities in the system
table layout.
Check your PATH to see where pg_dump is coming from...
regards, tom lane
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [NOVICE] pg_dump problem
@ 2000-07-22 14:16 John Burski <jburski@autopartshq.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 18+ messages in thread
From: John Burski @ 2000-07-22 14:16 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin; pgsql-novice@postgresql.org
Just the ticket!! I renamed the old "pg_dump" command in /usr/bin and
created a symbolic link to the "pg_dump" command in /usr/local/pgsql/bin
and, voila!, life is good!
Thanks, Tom!
Tom Lane wrote:
> John Burski <jburski@autopartshq.com> writes:
> > When I issue the "pg_dump jcon" (jcon being the database name, of
> > course) I receive the following error message:
>
> > getInherits(): SELECT failed
>
> It might be time to put this in the FAQ ;-). You're probably trying
> to run a 6.5 (or earlier?) pg_dump against a 7.0 database. The older
> pg_dump doesn't do any version checking, and the first it realizes
> it's got trouble is when it hits incompatibilities in the system
> table layout.
>
> Check your PATH to see where pg_dump is coming from...
>
> regards, tom lane
--
John R. Burski - (Title depends on the hat I'm wearing)
Automotive Parts Headquarters, Inc.
125 South 29th Avenue
Saint Cloud, MN 56301
320 252 5411 x137
Attachments:
smime.p7s (application/x-pkcs7-signature, 2.2K) download
^ permalink raw reply [nested|flat] 18+ messages in thread
* pg_dump problem
@ 2000-08-02 01:20 Paulo Roberto Siqueira <paulo.siqueira@usa.net>
0 siblings, 0 replies; 18+ messages in thread
From: Paulo Roberto Siqueira @ 2000-08-02 01:20 UTC (permalink / raw)
To: pgsql-admin
PgSQL 7.0.2
I used pg_dump to dump the schema of a db. I created table part_presencial
with this command
create table part_presencial(
login char(15) not null,
id_curso_polo int4 not null,
data_encontro date not null,
nota numeric(2,2) null,
foreign key(login,id_curso_polo) references matricula,
foreign key(id_curso_polo,data_encontro) references presencial,
primary key(login,id_curso_polo,data_encontro));
But pg_dump gives me this:
CREATE TABLE "part_presencial" (
"login" char(15) NOT NULL,
"id_curso_polo" int4 NOT NULL,
"data_encontro" date NOT NULL,
"nota" numeric(2,2),
PRIMARY KEY ("login", "id_curso_polo", "data_encontro")
);
Why doesn't pg_dump give me foreign keys constraints? It happens to all the
tables with foreign keys.
-----
Paulo Roberto Siqueira
paulo.siqueira@usa.net
Database Administrator
Goiania - GO - Brazil
^ permalink raw reply [nested|flat] 18+ messages in thread
* pg_dump problem
@ 2003-03-21 18:15 Tatiana Motova <t.motova@inform-link.co.uk>
0 siblings, 1 reply; 18+ messages in thread
From: Tatiana Motova @ 2003-03-21 18:15 UTC (permalink / raw)
To: pgsql-admin
Hi all,
i have a problem dumping the database containing blobs.
The database has pdf files stored in one of the tables and when there are let say 10 files in it, pg_dump works perfectly, but when about 400Mb of files are loaded into db, pg_dump fails with the following message:
pg_dump -a -b -Ft -f bdata_030321.tar -v mydb
...
pg_dump: [tar archiver] could not write to tar member (wrote 872, attempted 8191)
It's not a matter of available disk space, there's plenty of it.
Help, please!
T.
^ permalink raw reply [nested|flat] 18+ messages in thread
* pg_dump problem
@ 2003-03-24 10:47 Tatiana Motova <t.motova@inform-link.co.uk>
0 siblings, 0 replies; 18+ messages in thread
From: Tatiana Motova @ 2003-03-24 10:47 UTC (permalink / raw)
To: pgsql-admin
Hi all,
i have a problem dumping the database containing blobs.
The database has pdf files stored in one of the tables and when there are let say 10 files in it, pg_dump works perfectly, but when about 400Mb of files are loaded into db, pg_dump fails with the following message:
pg_dump -a -b -Ft -f bdata_030321.tar -v mydb
...
pg_dump: [tar archiver] could not write to tar member (wrote 872, attempted 8191)
It's not a matter of available disk space, there's plenty of it.
I'm using PostgreSQL 7.2.2 on Red Hat 8.0
Help, please!
T.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem
@ 2003-03-24 19:11 Robert Treat <xzilla@users.sourceforge.net>
parent: Tatiana Motova <t.motova@inform-link.co.uk>
0 siblings, 1 reply; 18+ messages in thread
From: Robert Treat @ 2003-03-24 19:11 UTC (permalink / raw)
To: Tatiana Motova <t.motova@inform-link.co.uk>; +Cc: pgsql-admin
On Fri, 2003-03-21 at 13:15, Tatiana Motova wrote:
> Hi all,
>
> i have a problem dumping the database containing blobs.
>
> The database has pdf files stored in one of the tables and when there
> are let say 10 files in it, pg_dump works perfectly, but when about
> 400Mb of files are loaded into db, pg_dump fails with the following
> message:
>
> pg_dump -a -b -Ft -f bdata_030321.tar -v mydb
> ...
> pg_dump: [tar archiver] could not write to tar member (wrote 872,
> attempted 8191)
>
> It's not a matter of available disk space, there's plenty of it.
>
Haven't seen any other response on this one.... This bug used to exist
in the 7.1.x versions, but I think it was fixed in one of the 7.2.x
releases. Can you post your version info? In the meantime you might be
able to work around it by using the -Fc instead.
Robert Treat
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem
@ 2003-03-24 19:17 Tatiana Motova <t.motova@inform-link.co.uk>
parent: Robert Treat <xzilla@users.sourceforge.net>
0 siblings, 1 reply; 18+ messages in thread
From: Tatiana Motova @ 2003-03-24 19:17 UTC (permalink / raw)
To: pgsql-admin
Version 7.2.2, i had same problems when using version 7.1.3 as well.
----- Original Message -----
From: "Robert Treat" <xzilla@users.sourceforge.net>
To: "Tatiana Motova" <t.motova@inform-link.co.uk>
Cc: <pgsql-admin@postgresql.org>
Sent: Monday, March 24, 2003 7:11 PM
Subject: Re: [ADMIN] pg_dump problem
> On Fri, 2003-03-21 at 13:15, Tatiana Motova wrote:
> > Hi all,
> >
> > i have a problem dumping the database containing blobs.
> >
> > The database has pdf files stored in one of the tables and when there
> > are let say 10 files in it, pg_dump works perfectly, but when about
> > 400Mb of files are loaded into db, pg_dump fails with the following
> > message:
> >
> > pg_dump -a -b -Ft -f bdata_030321.tar -v mydb
> > ...
> > pg_dump: [tar archiver] could not write to tar member (wrote 872,
> > attempted 8191)
> >
> > It's not a matter of available disk space, there's plenty of it.
> >
>
> Haven't seen any other response on this one.... This bug used to exist
> in the 7.1.x versions, but I think it was fixed in one of the 7.2.x
> releases. Can you post your version info? In the meantime you might be
> able to work around it by using the -Fc instead.
>
> Robert Treat
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem
@ 2003-03-27 20:13 Robert Treat <xzilla@users.sourceforge.net>
parent: Tatiana Motova <t.motova@inform-link.co.uk>
0 siblings, 1 reply; 18+ messages in thread
From: Robert Treat @ 2003-03-27 20:13 UTC (permalink / raw)
To: Tatiana Motova <t.motova@inform-link.co.uk>; +Cc: pgsql-admin
Did the -Fc workaround work? I tried to do a little digging to find out
the heart of the problem but didn't come up with much. You might want to
post to -bugs, or better yet try upgrading to 7.3
Robert Treat
On Mon, 2003-03-24 at 14:17, Tatiana Motova wrote:
> Version 7.2.2, i had same problems when using version 7.1.3 as well.
>
> ----- Original Message -----
> From: "Robert Treat" <xzilla@users.sourceforge.net>
> To: "Tatiana Motova" <t.motova@inform-link.co.uk>
> Cc: <pgsql-admin@postgresql.org>
> Sent: Monday, March 24, 2003 7:11 PM
> Subject: Re: [ADMIN] pg_dump problem
>
>
> > On Fri, 2003-03-21 at 13:15, Tatiana Motova wrote:
> > > Hi all,
> > >
> > > i have a problem dumping the database containing blobs.
> > >
> > > The database has pdf files stored in one of the tables and when there
> > > are let say 10 files in it, pg_dump works perfectly, but when about
> > > 400Mb of files are loaded into db, pg_dump fails with the following
> > > message:
> > >
> > > pg_dump -a -b -Ft -f bdata_030321.tar -v mydb
> > > ...
> > > pg_dump: [tar archiver] could not write to tar member (wrote 872,
> > > attempted 8191)
> > >
> > > It's not a matter of available disk space, there's plenty of it.
> > >
> >
> > Haven't seen any other response on this one.... This bug used to exist
> > in the 7.1.x versions, but I think it was fixed in one of the 7.2.x
> > releases. Can you post your version info? In the meantime you might be
> > able to work around it by using the -Fc instead.
> >
> > Robert Treat
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem
@ 2003-03-28 11:50 Tatiana Motova <t.motova@inform-link.co.uk>
parent: Robert Treat <xzilla@users.sourceforge.net>
0 siblings, 1 reply; 18+ messages in thread
From: Tatiana Motova @ 2003-03-28 11:50 UTC (permalink / raw)
To: Robert Treat <xzilla@users.sourceforge.net>; +Cc: pgsql-admin
Unfortunately not.
pg_dump makes it's work without reporting any errors with -Fc but pg_restore
fails:
pg_restore: [archiver (db)] error returned by PQputline
I could try upgrading to 7.3 but i need to keep the database data anyway.
Tatiana.
----- Original Message -----
From: "Robert Treat" <xzilla@users.sourceforge.net>
To: "Tatiana Motova" <t.motova@inform-link.co.uk>
Cc: <pgsql-admin@postgresql.org>
Sent: Thursday, March 27, 2003 8:13 PM
Subject: Re: [ADMIN] pg_dump problem
> Did the -Fc workaround work? I tried to do a little digging to find out
> the heart of the problem but didn't come up with much. You might want to
> post to -bugs, or better yet try upgrading to 7.3
>
> Robert Treat
>
> On Mon, 2003-03-24 at 14:17, Tatiana Motova wrote:
> > Version 7.2.2, i had same problems when using version 7.1.3 as well.
> >
> > ----- Original Message -----
> > From: "Robert Treat" <xzilla@users.sourceforge.net>
> > To: "Tatiana Motova" <t.motova@inform-link.co.uk>
> > Cc: <pgsql-admin@postgresql.org>
> > Sent: Monday, March 24, 2003 7:11 PM
> > Subject: Re: [ADMIN] pg_dump problem
> >
> >
> > > On Fri, 2003-03-21 at 13:15, Tatiana Motova wrote:
> > > > Hi all,
> > > >
> > > > i have a problem dumping the database containing blobs.
> > > >
> > > > The database has pdf files stored in one of the tables and when
there
> > > > are let say 10 files in it, pg_dump works perfectly, but when about
> > > > 400Mb of files are loaded into db, pg_dump fails with the following
> > > > message:
> > > >
> > > > pg_dump -a -b -Ft -f bdata_030321.tar -v mydb
> > > > ...
> > > > pg_dump: [tar archiver] could not write to tar member (wrote 872,
> > > > attempted 8191)
> > > >
> > > > It's not a matter of available disk space, there's plenty of it.
> > > >
> > >
> > > Haven't seen any other response on this one.... This bug used to exist
> > > in the 7.1.x versions, but I think it was fixed in one of the 7.2.x
> > > releases. Can you post your version info? In the meantime you might be
> > > able to work around it by using the -Fc instead.
> > >
> > > Robert Treat
>
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem
@ 2003-04-02 14:24 lists <lists@insyde.com.br>
parent: Tatiana Motova <t.motova@inform-link.co.uk>
0 siblings, 0 replies; 18+ messages in thread
From: lists @ 2003-04-02 14:24 UTC (permalink / raw)
To: Tatiana Motova <t.motova@inform-link.co.uk>; +Cc: pgsql-admin
I'm getting the same error... Is there any work around?
TIA
Ricardo.
----- Original Message -----
> Unfortunately not.
> pg_dump makes it's work without reporting any errors with -Fc but
pg_restore
> fails:
> pg_restore: [archiver (db)] error returned by PQputline
> I could try upgrading to 7.3 but i need to keep the database data anyway.
>
> Tatiana.
^ permalink raw reply [nested|flat] 18+ messages in thread
* pg_dump problem
@ 2004-01-10 12:29 Likit Younboon <likity@ttt.co.th>
0 siblings, 1 reply; 18+ messages in thread
From: Likit Younboon @ 2004-01-10 12:29 UTC (permalink / raw)
To: pgsql-admin
Hi,
I use PostgreSQL and use backup command (pg_dump).
I use like this $pg_dump -u -Fc -b databasename > backup.tar.gz
I need to backup with pg_dump by automatic with crontab, but pg_dump must input Username and Password.
How to bypass Username and Password for use pg_dump with crontab.
Please help me. I don't know how to solve problem.
Thank you.
Likit Younboon
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem
@ 2004-01-11 19:37 Peter Eisentraut <peter_e@gmx.net>
parent: Likit Younboon <likity@ttt.co.th>
0 siblings, 0 replies; 18+ messages in thread
From: Peter Eisentraut @ 2004-01-11 19:37 UTC (permalink / raw)
To: Likit Younboon <likity@ttt.co.th>; pgsql-admin
Likit Younboon wrote:
> How to bypass Username and Password for use pg_dump with crontab.
Preferrably, set your client authentication (pg_hba.conf) not to require
passwords. In newer versions you can also store user passwords in a
file ~/.pgpass.
^ permalink raw reply [nested|flat] 18+ messages in thread
* pg_dump problem.
@ 2005-03-20 14:34 Michael <cutemic@hotmail.com>
0 siblings, 1 reply; 18+ messages in thread
From: Michael @ 2005-03-20 14:34 UTC (permalink / raw)
To: pgsql-admin
Hi, all,
I run pg_dump -s to back up my database and get this error message:
pg_dump: could not parse ACL list ([0:1]={pgsql=UC/pgsql,=UC/pgsql}) for
object "public" (SCHEMA)
Can someone tell me why?
pgsql is the username.
postgresql version:pre-release version of postgresql 7.5 windows edition.
os: win xp pro.
Thanks in advance.
Best regrads,
Michael
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem.
@ 2005-03-21 02:57 Tom Lane <tgl@sss.pgh.pa.us>
parent: Michael <cutemic@hotmail.com>
0 siblings, 1 reply; 18+ messages in thread
From: Tom Lane @ 2005-03-21 02:57 UTC (permalink / raw)
To: Michael <cutemic@hotmail.com>; +Cc: pgsql-admin
"Michael" <cutemic@hotmail.com> writes:
> I run pg_dump -s to back up my database and get this error message:
> pg_dump: could not parse ACL list =
> ([0:1]=3D{pgsql=3DUC/pgsql,=3DUC/pgsql}) for=20
> object "public" (SCHEMA)=20
> Can someone tell me why?
You're using a buggy beta version.
regards, tom lane
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem.
@ 2005-03-21 17:56 Michael <cutemic@hotmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 18+ messages in thread
From: Michael @ 2005-03-21 17:56 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
Hi,
I download the latest version of postgresql (8.0 for windows) and fix the
problem.
But here comes another one.
The sql script I dump from v8.0 seems to be not full compatible with v7.4
used on the server. So I'm unable to update the database on the server to
the local one.
What can I do?
Regards,
Michael
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Michael" <cutemic@hotmail.com>
Cc: <pgsql-admin@postgresql.org>
Sent: 2005年3月21日 星期一 10:57
Subject: Re: [ADMIN] pg_dump problem.
| "Michael" <cutemic@hotmail.com> writes:
| > I run pg_dump -s to back up my database and get this error message:
|
| > pg_dump: could not parse ACL list =
| > ([0:1]=3D{pgsql=3DUC/pgsql,=3DUC/pgsql}) for=20
| > object "public" (SCHEMA)=20
|
| > Can someone tell me why?
|
| You're using a buggy beta version.
|
| regards, tom lane
|
| ---------------------------(end of broadcast)---------------------------
| TIP 4: Don't 'kill -9' the postmaster
|
^ permalink raw reply [nested|flat] 18+ messages in thread
* pg_dump problem
@ 2006-08-06 14:47 Srinivas Iyyer <srini_iyyer_bio@yahoo.com>
0 siblings, 1 reply; 18+ messages in thread
From: Srinivas Iyyer @ 2006-08-06 14:47 UTC (permalink / raw)
To: pgsql-admin
Dear group,
I have two databases in my system.
In firstdb i am having the following problem:
firstdb=# \d targets
ERROR: could not access status of transaction 362
DETAIL: could not open file
"/var/lib/pgsql/data/pg_clog/0000": No such file or
directory
when I vacuumed it:
$ vacuumdb firstdb
vacuumdb: vacuuming of database "firstdb" failed:
ERROR: could not access status of transaction 11
DETAIL: could not open file
"/var/lib/pgsql/data/pg_clog/0000": No such file or
directory
Second problem:
Issue with secondb - arraydb
$ vacuumdb arraydb
VACUUM
Suspecting there is something going on with
postgres,
I wanted to take a backup of the arraydb.
here is what I am doing:
$ sudo pg_dump arraydb >
arraydb_bcup_Aug_05_2006.dump
There is nothing in this. I created dumps long back
and they are heavy.
I restarted the postgre server /etc/init.d/postgres
restart Despite this, I am having problems.
$ ls -lh
total 8.0K
-rw-r--r-- 1 speri postgres 0 Aug 5 20:17
arradb_bcup_Aug_05_2006.out
What is in the /var/lib/pgsql/data/pg_clog
$ sudo ls -lh /var/lib/pgsql/data/pg_clog
total 80K
-rw------- 1 postgres postgres 72K Aug 5 20:12 0001
Logs:
Surprisingly my logs is empty . Is this because I
restarted the server.
what could be the problem in the cases of first and
second problems.
looking forward to hear from experts eagerly.
Thanks
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: pg_dump problem
@ 2006-08-08 16:47 Jim Nasby <jnasby@pervasive.com>
parent: Srinivas Iyyer <srini_iyyer_bio@yahoo.com>
0 siblings, 0 replies; 18+ messages in thread
From: Jim Nasby @ 2006-08-08 16:47 UTC (permalink / raw)
To: Srinivas Iyyer <srini_iyyer_bio@yahoo.com>; +Cc: pgsql-admin
On Aug 6, 2006, at 9:47 AM, Srinivas Iyyer wrote:
> I have two databases in my system.
>
> In firstdb i am having the following problem:
> firstdb=# \d targets
> ERROR: could not access status of transaction 362
> DETAIL: could not open file
> "/var/lib/pgsql/data/pg_clog/0000": No such file or
> directory
>
> when I vacuumed it:
> $ vacuumdb firstdb
> vacuumdb: vacuuming of database "firstdb" failed:
> ERROR: could not access status of transaction 11
> DETAIL: could not open file
> "/var/lib/pgsql/data/pg_clog/0000": No such file or
> directory
You didn't mention what version you're using, but this sounds a lot
like a corruption problem.
> Second problem:
>
> Issue with secondb - arraydb
>
> $ vacuumdb arraydb
> VACUUM
>
> Suspecting there is something going on with
> postgres,
> I wanted to take a backup of the arraydb.
>
> here is what I am doing:
>
> $ sudo pg_dump arraydb >
> arraydb_bcup_Aug_05_2006.dump
>
> There is nothing in this. I created dumps long back
> and they are heavy.
> I restarted the postgre server /etc/init.d/postgres
> restart Despite this, I am having problems.
>
> $ ls -lh
> total 8.0K
> -rw-r--r-- 1 speri postgres 0 Aug 5 20:17
> arradb_bcup_Aug_05_2006.out
Just where did that out file come from?
> What is in the /var/lib/pgsql/data/pg_clog
> $ sudo ls -lh /var/lib/pgsql/data/pg_clog
> total 80K
> -rw------- 1 postgres postgres 72K Aug 5 20:12 0001
>
> Logs:
>
> Surprisingly my logs is empty . Is this because I
> restarted the server.
Probably not, unless it's something the init.d script (which we have
nothing to do with) is doing. You probably have logging mis-
configured, or you're looking in the wrong place.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
^ permalink raw reply [nested|flat] 18+ messages in thread
end of thread, other threads:[~2006-08-08 16:47 UTC | newest]
Thread overview: 18+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-07-21 19:38 pg_dump problem John Burski <jburski@autopartshq.com>
2000-07-21 22:05 ` Tom Lane <tgl@sss.pgh.pa.us>
2000-07-22 14:16 ` John Burski <jburski@autopartshq.com>
2000-08-02 01:20 pg_dump problem Paulo Roberto Siqueira <paulo.siqueira@usa.net>
2003-03-21 18:15 pg_dump problem Tatiana Motova <t.motova@inform-link.co.uk>
2003-03-24 19:11 ` Robert Treat <xzilla@users.sourceforge.net>
2003-03-24 19:17 ` Tatiana Motova <t.motova@inform-link.co.uk>
2003-03-27 20:13 ` Robert Treat <xzilla@users.sourceforge.net>
2003-03-28 11:50 ` Tatiana Motova <t.motova@inform-link.co.uk>
2003-04-02 14:24 ` lists <lists@insyde.com.br>
2003-03-24 10:47 pg_dump problem Tatiana Motova <t.motova@inform-link.co.uk>
2004-01-10 12:29 pg_dump problem Likit Younboon <likity@ttt.co.th>
2004-01-11 19:37 ` Peter Eisentraut <peter_e@gmx.net>
2005-03-20 14:34 pg_dump problem. Michael <cutemic@hotmail.com>
2005-03-21 02:57 ` Re: pg_dump problem. Tom Lane <tgl@sss.pgh.pa.us>
2005-03-21 17:56 ` Re: pg_dump problem. Michael <cutemic@hotmail.com>
2006-08-06 14:47 pg_dump problem Srinivas Iyyer <srini_iyyer_bio@yahoo.com>
2006-08-08 16:47 ` Jim Nasby <jnasby@pervasive.com>
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