From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a05:620a:634:: with SMTP id 20mr24007610qkv.330.1572976279599; Tue, 05 Nov 2019 09:51:19 -0800 (PST) X-Received: by 2002:aca:4891:: with SMTP id v139mr134908oia.175.1572976279365; Tue, 05 Nov 2019 09:51:19 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.dns-netz.com!news.freedyn.net!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!j16no2940729qtl.0!news-out.google.com!p4ni264qtu.1!nntp.google.com!j16no2940714qtl.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 5 Nov 2019 09:51:19 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=146.5.2.231; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 146.5.2.231 References: <32accab7-f2cf-4eba-b4b6-642dd4ea81b3@googlegroups.com> <04dd75bd-7c90-467f-b729-ca79e1377d0a@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: how would gnoga.com beat www.tck.tk and postgresql on freebsd? From: Shark8 Injection-Date: Tue, 05 Nov 2019 17:51:19 +0000 Content-Type: text/plain; charset="UTF-8" X-Received-Bytes: 1934 X-Received-Body-CRC: 3569478649 Xref: reader01.eternal-september.org comp.lang.ada:57495 Date: 2019-11-05T09:51:19-08:00 List-Id: On Tuesday, November 5, 2019 at 10:31:59 AM UTC-7, Dmitry A. Kazakov wrote: > On 2019-11-05 18:11, Shark8 wrote: > > > Yes: Gnoga's DB bindings + migration protocol is *VERY* good for reducing errors. It would be even fewer if I can get NMESON (pure-Ada graph-based database) modernized and integrated into Gnoga. > > On a lesser scale persistent B-trees, persistent memory pool should > already be available in Gnoga via Simple Components. Oh, nice! I may have to look into that.