Changes between Version 5 and Version 6 of drmsSumRm

Timestamp:

09/11/14 14:13:13 (10 years ago)

Author:

joe

Comment:

added new check for how many sunums could be cleaned up + trigger to keep effective_date low.

drmsSumRm

@@ -26 +26 @@
 }}}
 
-to ascertain if this may be the case.
+to ascertain if this may be the case.  You can also try:
+
+{{{
+select count(*) from sum_partn_alloc where effective_date < to_char( now(), 'YYYYMMDDHH24MI' );
+}}}
+
+
+
 
 The configuration file for sum_rm is below :
@@ -101 +108 @@
 NORUN_STOP=7
 }}}
+
+
+----
+
+If you are setting SUMS up on a test server that doesn't have much disk space, the following trigger can be used to ensure that the SUMS effective_date is kept low enough to ensure sum_rm can clean up:
+
+{{{
+CREATE OR REPLACE FUNCTION no_retention ( ) RETURNS TRIGGER LANGUAGE PLPGSQL AS $$
+BEGIN
+NEW.effective_date := to_char( (now()+INTERVAL '2 hours'), 'YYYYMMDDHH24MI' );
+END
+$$;
+
+CREATE TRIGGER no_retention BEFORE INSERT ON sum_partn_alloc FOR EACH ROW EXECUTE PROCEDURE no_retention();
+}}}