Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gnyMt-0001fa-33 for pgsql-advocacy@arkaria.postgresql.org; Mon, 28 Jan 2019 04:17:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gnyMr-0004Xw-U0 for pgsql-advocacy@arkaria.postgresql.org; Mon, 28 Jan 2019 04:17:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gnyMr-0004Xb-Lg for pgsql-advocacy@lists.postgresql.org; Mon, 28 Jan 2019 04:17:53 +0000 Received: from mail-lf1-x142.google.com ([2a00:1450:4864:20::142]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gnyMo-0008Nw-Oo for pgsql-advocacy@lists.postgresql.org; Mon, 28 Jan 2019 04:17:52 +0000 Received: by mail-lf1-x142.google.com with SMTP id v5so10797349lfe.7 for ; Sun, 27 Jan 2019 20:17:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8K/QLVDXUlE2NVBzNUzCDtsWTvJb4uYil/zHayuADf0=; b=BRAx6zcFIP3jYlA/V+6DXffKobfcdeBXqWorev6OpyR+1+PZmWWCyro+HVZrnnxYvT QzXs+u58vsJIoz7fMB7jyv6Opji7qm82PlbXE5w5yuhjreIGQ5e5+L7VbuSZqoKHSXER jVr2dE/yoHJXBlmY/NT0wpZ/dmPCeksXYbgwV/+A7e6YaIY3CzFYjuwsoz48iNjRPpNA oxbNLralpa5JU6Ib8ICPhzLFSDNYcTbTzUJcFBzqc3YZVOlUNkSbG9wRWD5UMdmKqWst iZ6eG/k1PBkeoZqb3tpizpWVAdjJEc730ctHKnrFiDPxphL0cb8fzrCX0rRaZTuI4E8r czsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8K/QLVDXUlE2NVBzNUzCDtsWTvJb4uYil/zHayuADf0=; b=sjb3vYxzld0K9alzKOMTwfyoV1ZDCOjUEdCANoCK0jiG6oWdCc1/h+cPq3roa+xDxW AvKGPfrhYfSARPal/IwNnohwJtIThj8cxEQb7DxhaC5uIPJXfAUHYKNTBIyNDp9Ul87+ EKEW7qqNL/wqUc778uCCKY5wlq0pSkEquTieelblO4WMWTNVLyxq7mNXWHURCWWqXI3g PVaCJ0v+RQmreU3z5/P5iSyXlpwP83C1Bq9nDNgn845G+0n0xWly40A6YQCNq16c5hQ9 Fl+wpVK1hxu9aF1aFpvmEIH3JAN8JaKKyQ3FW8CN8aVr0AjYS/qQwnx9WrEoV+E0KJEf HFNQ== X-Gm-Message-State: AJcUukdSqW1AimNAK3SemIGBQBnaF2NGDOoXacXNIeJXrYKvIzIWgx2J Au6Y/mjDVXSMnCwBj4rE8hfwZk1xIn7iavQs/tY= X-Google-Smtp-Source: ALg8bN40zt7Limww9dajyddHtm5daI5393HiM16bE2naqBADA9ufHRxdUQOViMSTEKyDCvTkNk+QFRkvoU52XPyMphc= X-Received: by 2002:a19:f89:: with SMTP id 9mr14971551lfp.10.1548649068742; Sun, 27 Jan 2019 20:17:48 -0800 (PST) MIME-Version: 1.0 References: <201901251516.m76emdb6ek2p@alvherre.pgsql> <86a17d2b6efb86bf7ebd7cf385981e79@postgresql.org> <20190126141212.GA672@fritz.box> In-Reply-To: From: Robert Haas Date: Sun, 27 Jan 2019 23:17:37 -0500 Message-ID: Subject: Re: Citus Data becomes Microsoft To: Justin Clift Cc: Michael Meskes , Alvaro Herrera , "Tsunakawa, Takayuki" , "pgsql-advocacy@lists.postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sat, Jan 26, 2019 at 10:48 AM Justin Clift wrote: > On 2019-01-27 01:12, Michael Meskes wrote: > > > Does this one bad behaviour make them an evil organisation per se? > > How about, does their continual bad behaviour - which is extremely > well documented over *decades* - of which this is one action... > warrant any kind of good will towards them? I don't think this conversation is really helping us figure anything out. I think it's an open question whether Microsoft acquiring Citus is good or bad for PostgreSQL, and I think that question probably deserves some sober reflection, as does the related question of whether Amazon acquiring OpenSCG is good or bad for PostgreSQL, but I disagree that the particular points that you mention answer that question. If Microsoft acquiring Citus is bad for PostgreSQL, it's probably got to do with whether there are viable independent PostgreSQL companies out there that can serve as employers for people who want to get paid to work on PostgreSQL, not whether or not they added social networking features to Github. If it's good for PostgreSQL, it's probably got to do with the value of having really large companies interested in this database that used to be basically the domain of hobbyists but is now big business. Or maybe it's a little of both? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company