On Sun, Mar 7, 2010 at 1:45 AM, Allan Kamau <kamauallan@xxxxxxxxx> wrote: > Hi, > I am looking for an efficient and effective solution to eliminate > duplicates in a continuously updated "cumulative" transaction table > (no deletions are envisioned as all non-redundant records are > important). Below is my situation. Is there a reason you can't use a unique index and detect failed inserts and reject them? -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
