| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Suggested "easy" TODO: pg_dump --from-list |
| Date: | 2010-11-26 18:59:36 |
| Message-ID: | m2tyj3oqqv.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dmitriy Igrishin <dmitigr(at)gmail(dot)com> writes:
> Without some "restoreddl" which able to "compile" the set of
> database objects from many files this tool (getddl) does nothing
> because another developer can change the database directly
Indeed, getddl does not try to solve that issue. It's more a VCS and
editor friendly export, to be able to see diffs that come from the real
current database state rather than what your code tracking makes you
think is in production already.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-11-26 19:06:18 | Re: Assertion failure on hot standby |
| Previous Message | Bruce Momjian | 2010-11-26 18:27:22 | Re: duplicate connection failure messages |