| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)gluefinance(dot)com> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_depend explained |
| Date: | 2011-01-12 13:07:47 |
| Message-ID: | 1294837502-sup-1771@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Joel Jacobson's message of mié ene 12 07:07:35 -0300 2011:
> The automatically created objects, such as primary key indexes,
> constraints and triggers, have been ignored in this graph, as they are
> implicitly created when creating the "base objects".
FWIW this idea fails when you consider stuff such as circular foreign
keys (and I suppose there are other, more common cases). If you really
want something general you need to break those apart. (This is the
explanation for the “break the loop” code in pg_dump I imagine)
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Klyukin | 2011-01-12 13:14:17 | Re: arrays as pl/perl input arguments [PATCH] |
| Previous Message | Dan Ports | 2011-01-12 12:53:22 | Re: SSI and 2PC |