From: | "Tomi N/A" <hefest(at)gmail(dot)com> |
---|---|
To: | "Dave Cramer" <pg(at)fastcrypt(dot)com> |
Cc: | "Marc Herbert" <Marc(dot)Herbert(at)continuent(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Backup with Java |
Date: | 2006-11-30 17:15:27 |
Message-ID: | d487eb8e0611300915g7c677056scb3afaf264ef035d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
2006/11/30, Dave Cramer <pg(at)fastcrypt(dot)com>:
> That could certainly be changed much easier than duplicating the
> entire pg_dump functionality
Yeah, but the way this have been architected, it's impossible to do a
backup over the network, i.e. with only the 5432 port at your
disposal. And that's just one of the _obvious_ drawbacks...the way I
see it, the way to do it would be to move the dump code into the
database server. Let _the_server_ do all the hard work and let the
application on the other end do whatever it wants with the (supposedly
plain text) dump. That's flexibility, and it wouldn't require
rewriting the dump utility - just a move into the server itself.
t.n.a.
From | Date | Subject | |
---|---|---|---|
Next Message | Csaba Nagy | 2006-11-30 17:24:15 | Re: Backup with Java |
Previous Message | Dave Cramer | 2006-11-30 16:16:54 | Re: Backup with Java |