pg_depend explained - Mailing list pgsql-hackers

From Joel Jacobson
Subject pg_depend explained
Date
Msg-id AANLkTinwsB5X=wm3+DjEtcc0hUipguPscenhEYC-BoE1@mail.gmail.com
Whole thread Raw
Responses Re: pg_depend explained  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_depend explained  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
Has anyone written a in-depth description on how to traverse the pg_depend tree?
The 'a' and 'i' deptype really makes it hard to figure out the
dependency order, a topological sort does not work.

My latest attempt involved trying to group by all objects connected to
each other via deptype 'a' or 'i', and replacing all such nodes in the
tree with the "source node", i.e. the node which according to the
topological order could be created first.

Am I on the right path, trying to "fuse" the internal/auto objects
together, replacing them with the top most object in the tree?
Or is there a simplier way to figure out the order in which objects
can be created?

I need a general solution, not a custom-made query for each regclass,
which is quite trivial but feels far from bullet proof, I want
something only relying on pg_depend, since it should be the safest
method of them all.

-- 
Best regards,

Joel Jacobson
Glue Finance


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: casts: max double precision > text > double precision fails with out or range error
Next
From: Garick Hamlin
Date:
Subject: Re: Streaming base backups