| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Marlon Petry <marlonpetry(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Backup and restore through JDBC |
| Date: | 2006-09-29 15:19:09 |
| Message-ID: | 16320.1159543149@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Then after you recover from your head exploding you start devising some
> sort of sane API ...
That's the hard part. There is no percentage in having a library if
it doesn't do anything significantly different from what you could
accomplish via
system("pg_dump ...switches....");
What is it you hope to accomplish by having a library, exactly?
(And don't say "more control over the dump process". pg_dump is already
on the hairy edge of maintainability; we do *not* need to try to deal
with making it still function correctly after an application programmer
makes some random intervention in the process.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-29 15:40:32 | Re: Another idea for dealing with cmin/cmax |
| Previous Message | Paul B. Anderson | 2006-09-29 15:12:08 | Re: Stored procedure array limits |