bdr: fix the possibly broken^Conflict history sequence in upgrade script
authorPetr Jelinek <pjmodos@pjmodos.net>
Fri, 29 Aug 2014 14:58:22 +0000 (16:58 +0200)
committerAndres Freund <andres@anarazel.de>
Mon, 8 Sep 2014 15:49:59 +0000 (17:49 +0200)
See 766e3bcb3c3c37981b12f93d0e4210213fa281c2 for more info.

bdr--0.7--0.7.1.sql

index 878cfdd4cdfe2f1a17cde880bb6534eab7710928..1e37ad6206c21434450344cd3f0b24460535ca8e 100644 (file)
@@ -4,3 +4,10 @@ DO $$BEGIN
 EXCEPTION WHEN duplicate_function THEN
    RETURN;
 END$$;
+
+BEGIN;
+SET LOCAL bdr.skip_ddl_replication = true;
+SET LOCAL bdr.permit_unsafe_ddl_commands = true;
+ALTER SEQUENCE bdr.bdr_conflict_history_id_seq USING local;
+SELECT setval('bdr.bdr_conflict_history_id_seq', (SELECT coalesce(max(conflict_id)+1,1) FROM bdr.bdr_conflict_history));
+COMMIT;