From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Andres Freund <andres@anarazel.de>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Gavin Flower <GavinFlower@archidevsys.co.nz>
Cc: dandl <david@andl.org>
Cc: Adam Brusselback <adambrusselback@gmail.com>
Cc: Joy Arulraj <jarulraj@cs.cmu.edu>
Cc: kang joni <kangjoni76@gmail.com>
Cc: Dmitry Igrishin <dmitigr@gmail.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Cc: Peter Eisentraut <peter_e@gmx.net>
Subject: Re: [GENERAL] C++ port of Postgres
Date: Tue, 16 Aug 2016 15:48:00 -0500
Message-ID: <b3ac88d1-5913-cc9f-5485-63413f82a685@BlueTreble.com> (raw)
In-Reply-To: <20160816202928.v62426ta2w4yauk7@alap3.anarazel.de>
References: <CABgyVxCorVSTkVcjkPS06YYt9bPPamGNXAsQkCDFKXGvXZDh-w@mail.gmail.com>
<CABgyVxCrHpk5SkU+7pVhze=dukx2SKqKNY8aOJstwaCRh=Y0Lg@mail.gmail.com>
<CABgyVxBA24NnPri8BYQFjVdn2pgqcB=Q6MXFXdcwchUmJSAUPw@mail.gmail.com>
<CAOmy0wLcyE3d=jbfpgoKtTicGoZ64AKKfEkG+ccXxtmajSBGeQ@mail.gmail.com>
<CABgyVxBjX6VbnbHfZRSDJBav4xKH5vSLZqTpr989sMOb+jX+jA@mail.gmail.com>
<CAMjNa7e7E81T3NqoReixYxrCFQpfWd+Mht0NhetW3bJB=Gs7Og@mail.gmail.com>
<007001d1f786$d903fa90$8b0befb0$@andl.org>
<00a52208-3199-5858-8846-2530b0bb34df@archidevsys.co.nz>
<f7682c24-4271-1ff5-d963-053ecb0fce40@BlueTreble.com>
<dc660b8e-bf78-9653-c5c1-39331f050d58@iki.fi>
<20160816202928.v62426ta2w4yauk7@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 8/16/16 3:29 PM, Andres Freund wrote:
> Well, having typed pg_list.h style lists, ilist.h linked lists,
> hash-tables, and proper typechecks for pg_nodes.h instead of the NodeTag
> stuff, would surely make life easier.
I certainly wish parts of the system brought code and "data" together in
a better way. Nodes are an example; all the Walker stuff in the
planner/executor is another. (I'm not saying C++ would make that better,
just saying those are parts of the code I find it much harder to grok.)
> But given the small subset of C++ available on all our supported
> platforms... I think we'd first need to make the decision to cut support
> for some platforms, before using C++. Which imo is a distinct task from
> *allowing* to compile with a C++ compiler.
Exactly. If we at least maintain support for compiling that means people
can experiment with other enhancements in a way that's much more
compatible with normal community contribution practices, which makes it
far more likely for that stuff to be accepted.
As for the backwards compatibility... the stance I've seen the community
take is cost vs benefit. Right now the benefits are completely
hypothetical, because no one could realistically propose a patch to use
C++ (or maybe even Rust) features.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, andres@anarazel.de, hlinnaka@iki.fi, GavinFlower@archidevsys.co.nz, david@andl.org, adambrusselback@gmail.com, jarulraj@cs.cmu.edu, kangjoni76@gmail.com, dmitigr@gmail.com, pgsql-hackers@postgresql.org, peter_e@gmx.net
Subject: Re: [GENERAL] C++ port of Postgres
In-Reply-To: <b3ac88d1-5913-cc9f-5485-63413f82a685@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox