Thread: why no answer? [Fwd: backup and restore just with use of jdbc?]

-------- Original-Nachricht --------

Betreff:	[GENERAL] backup and restore just with use of jdbc?
Datum:	Sun, 13 Jun 2004 10:23:53 +0200
Von:	zuhans@iname.com <zuhans@iname.com>
An:	pgsql-general@postgresql.org

hello,

is there a way to do backup and restore just with the use of jdbc?

greetings
hans

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
             http://archives.postgresql.org

> is there a way to do backup and restore just with the use of jdbc?
>

No.

Kris Jurka

zuhans@iname.com ("zuhans@iname.com") writes:
> is there a way to do backup and restore just with the use of jdbc?

You could presumably reimplement pg_dump in Java; that seems redundant
in view of the fact that pg_dump is already implemented in C.
--
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://cbbrowne.com/info/spreadsheets.html
"Very funny, Scotty. Now beam down my clothes."

hello,

thank you for your short - but informative - answers!
i don't know why this very very important thing isn't implemented by the jdbc (and other...) driver. it shouldn't only be managable by those sitting in front of the machine but also via my program to handle some critical situation in the way i want it to be done (and if i hoste my webapp somewhere in another continent, i won't be able to sit in front of the servers console-screen).

to recode pg_dump is far off my time and (maybe) skills. why isn't it implemented for easier access?

greetings
hans



Chris Browne schrieb:

zuhans@iname.com ("zuhans@iname.com") writes: 

is there a way to do backup and restore just with the use of jdbc?   

You could presumably reimplement pg_dump in Java; that seems redundant
in view of the fact that pg_dump is already implemented in C. 

On Wed, 2004-06-16 at 23:28, zuhans@iname.com wrote:
> hello,
>
> thank you for your short - but informative - answers!
> i don't know why this very very important thing isn't implemented by
> the jdbc (and other...) driver. it shouldn't only be managable by
> those sitting in front of the machine but also via my program to
> handle some critical situation in the way i want it to be done (and if
> i hoste my webapp somewhere in another continent, i won't be able to
> sit in front of the servers console-screen).
>
> to recode pg_dump is far off my time and (maybe) skills. why isn't it
> implemented for easier access?

Well, pg_dump doesn't have to be run on the server, it can be run on a
client halfway around the world from the server and work just fine.

hello scott,

this is good news (for me ;-) )!
what kind of client should be available (if i search for a good hoster in near future)?

greetings
hans



Scott Marlowe schrieb:

On Wed, 2004-06-16 at 23:28, zuhans@iname.com wrote: 

hello,

thank you for your short - but informative - answers!
i don't know why this very very important thing isn't implemented by
the jdbc (and other...) driver. it shouldn't only be managable by
those sitting in front of the machine but also via my program to
handle some critical situation in the way i want it to be done (and if
i hoste my webapp somewhere in another continent, i won't be able to
sit in front of the servers console-screen).

to recode pg_dump is far off my time and (maybe) skills. why isn't it
implemented for easier access?   

Well, pg_dump doesn't have to be run on the server, it can be run on a
client halfway around the world from the server and work just fine.


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your     joining column's datatypes do not match
 

zuhans@iname.com wrote:
> hello scott,
>
> this is good news (for me ;-) )!
> what kind of client should be available (if i search for a good hoster
> in near future)?
>
> greetings
> hans

Here are the programs installed by postgres.  If psql is installed
by your hoster, the others are probably available as well.

~/pg/bin$ ls
clusterdb   dropdb    initdb        pg_controldata  pg_encoding   postgres
createdb    droplang  initlocation  pg_ctl        pg_id      postmaster
createlang  dropuser  ipcclean        pg_dump        pg_resetxlog  psql
createuser  ecpg      pg_config     pg_dumpall        pg_restore      vacuumdb

HTH!
Mark