| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), |
| Date: | 2006-06-12 16:27:26 |
| Message-ID: | 448D95EE.5040903@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> Before we pull pg_dump to bits let's identify some actual benefit from
> doing so. If you look at the code you will see that it is more than
> somewhat complex. A large scale move like you are proposing would be
> very high risk, IMNSHO.
From a person who deals with customer migrations daily perspective.
Anything that is going to put the stability and integrity of
pg_dump/pg_restore in *any* way, is a no op.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-06-12 17:12:59 | CSV mode option for pg_dump |
| Previous Message | Mark Cave-Ayland | 2006-06-12 16:13:24 | Re: Proposal for debugging of server-side stored procedures |