Enabling operator dropping in the moc-vs-geometry SQL.

I hadn't done this before because the warnings spoiled the regression
expectation.  I'm now shutting those up for while I'm doing the dropping.

Author: msdemlei

pgs_moc_geo_casts.sql.in

@@ -6,23 +6,26 @@
 
 -- #################################
 -- Cleanup
--- DROP OPERATOR IF EXISTS
---     <@ (smoc, scircle),
---     <@ (scircle, smoc),
---     <@ (smoc, spoly),
---     <@ (spoly, smoc),
---     !<@ (smoc, scircle),
---     !<@ (scircle, smoc),
---     !<@ (smoc, spoly),
---     !<@ (spoly, smoc),
---     @> (smoc, scircle),
---     @> (scircle, smoc),
---     @> (smoc, spoly),
---     @> (spoly, smoc),
---     !@> (smoc, scircle),
---     !@> (scircle, smoc),
---    !@> (smoc, spoly),
---    !@> (spoly, smoc);
+
+set client_min_messages = 'warning';
+DROP OPERATOR IF EXISTS
+    <@ (smoc, scircle),
+    <@ (scircle, smoc),
+    <@ (smoc, spoly),
+    <@ (spoly, smoc),
+    !<@ (smoc, scircle),
+    !<@ (scircle, smoc),
+    !<@ (smoc, spoly),
+    !<@ (spoly, smoc),
+    @> (smoc, scircle),
+    @> (scircle, smoc),
+    @> (smoc, spoly),
+    @> (spoly, smoc),
+    !@> (smoc, scircle),
+    !@> (scircle, smoc),
+    !@> (smoc, spoly),
+    !@> (spoly, smoc);
+reset client_min_messages;
 
 -- #################################
 --  smoc/geo OVERLAPS