Refactor the handling of the various DropStmt variants so that when multiple

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 0cefb50f3ce964d6097aad64dabd9b544c3d2e68
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2008-06-14T18:04:34Z
Releases: 8.4.0
Refactor the handling of the various DropStmt variants so that when multiple
objects are specified, we drop them all in a single performMultipleDeletions
call.  This makes the RESTRICT/CASCADE checks more relaxed: it's not counted
as a cascade if one of the later objects has a dependency on an earlier one.
NOTICE messages about such cases go away, too.

In passing, fix the permissions check for DROP CONVERSION, which for some
reason was never made role-aware, and omitted the namespace-owner exemption
too.

Alex Hunsaker, with further fiddling by me.

Files