Re: pg_depend explained

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joel Jacobson <joel(at)gluefinance(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_depend explained
Date: 2011-01-12 18:06:59
Message-ID: 28806.1294855619@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joel Jacobson <joel(at)gluefinance(dot)com> writes:
> 2011/1/12 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> This isn't particularly *useful*, maybe, but it's hardly "impossible".
>> And if we analyzed function dependencies in any detail, circular
>> dependencies among functions would be possible (and useful).

> Thanks Tom for clarifying, this makes me even more motivated into
> implementing the "creation order"-algorithm using only sql/plpgsql and
> pg_depend.
> If you have any ideas on how to do this, in addition to reading the
> dependency.c and pg_dump_sort.c source code, they would be highly
> appreciated.

I've sometimes found it useful to think of internal dependencies as
acting like normal dependencies pointing in the other direction.
I'm not sure that would do much to solve your problem, but it might
be worth trying.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-01-12 18:12:48 Re: libpq documentation cleanups (repost 3)
Previous Message Stephen Frost 2011-01-12 17:59:57 Re: Add support for logging the current role