Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Ok, this patch implements more or less this idea; except that instead of
> checking the list of implicit dependencies for later objects, we iterate
> twice on the list of objects to delete, and create a list of implicit
> dependencies on all of them the first time, and delete those not on that
> list the second time.

In the light of morning it occurs to me that probably the best code
factoring for this is for dependency.c to export a
performMultipleDeletions() function that takes an objectAddresses list
of targets and does all the dependency-chasing internally.  This would
reduce the amount of cruft that has to be exported from dependency.c.

Other than that, the patch looks plausible in a very fast scan.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to