From d1226a3fed243a335b724b06c10a9b6ff64c66d0 Mon Sep 17 00:00:00 2001 From: Craig Ringer Date: Tue, 24 Mar 2015 14:47:31 +0800 Subject: [PATCH] doc: Remove superceded distributed sequences docs --- doc/filelist.sgml | 1 - doc/manual-distributed-sequences.sgml | 24 ------------------------ 2 files changed, 25 deletions(-) delete mode 100644 doc/manual-distributed-sequences.sgml diff --git a/doc/filelist.sgml b/doc/filelist.sgml index 012b241095..bc6b943b44 100644 --- a/doc/filelist.sgml +++ b/doc/filelist.sgml @@ -42,7 +42,6 @@ - diff --git a/doc/manual-distributed-sequences.sgml b/doc/manual-distributed-sequences.sgml deleted file mode 100644 index f3ac8ab199..0000000000 --- a/doc/manual-distributed-sequences.sgml +++ /dev/null @@ -1,24 +0,0 @@ - - Distributed Sequences - - Distributed Sequences - - - In a asynchronous multimaster environment it can be hard to - have generated surrogate keys without a chance of - conflicts. Possible solutions includee using random - identifiers (like UUIDs) and assigning large ranges of values - to individual nodes. - - - - &bdr; provides distributed sequences - as a solution for that problem, without preventing - implementation of other solutions. These assign small ranges - of values to individual nodes, which these than can hand out - during inserts. To make usage of these as simple as possible - all that has to be done to use these, in comparison to normal - sequences, is to specify the USING bdr - option when creating a sequence. - - -- 2.39.5