Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qeANT-005y3D-RU for pgsql-advocacy@arkaria.postgresql.org; Thu, 07 Sep 2023 08:28:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qeANS-00H04X-GV for pgsql-advocacy@arkaria.postgresql.org; Thu, 07 Sep 2023 08:28:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qeANS-00H04I-4G for pgsql-advocacy@lists.postgresql.org; Thu, 07 Sep 2023 08:28:38 +0000 Received: from mail-ed1-x531.google.com ([2a00:1450:4864:20::531]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qeANO-003DV8-H4 for pgsql-advocacy@lists.postgresql.org; Thu, 07 Sep 2023 08:28:36 +0000 Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-52bcd4db4e6so843285a12.0 for ; Thu, 07 Sep 2023 01:28:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1694075313; x=1694680113; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GbrwgO8temB94d+zM/05bBKq1kkQReBna9uOZM1ir3U=; b=kGV+1Rg3pLJ92OsMIK82aNK1pIj/k/a3/dxyi1EVaPY+6bev5sgf26Cv1e9GNIF2YP w9Ed+0WbPUiWhAZ4k5IXAMsV1Nj6USZ5qejKfCDiYpYZKr+vurNrzndk12uO6K3FdeJo T25SdNGzp5baD7gsn1ACpxV6svfNuDq07FWqYP6fH4+4orUAPYZeJAQDBJCKE26dAuE6 ggSYX1VHe7Ic1mwaSA8jt97lLUTkt0b6gKW+atYn4lN8Ew15HhYeTEMcCphaQeE7UM9s 1ZjPbqfq8mtMyHAWc421pC0T1lYOOPglMhXPKtrcCoV6VmTPYHyANhNcUqYpdFgXZRFl Haig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694075313; x=1694680113; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GbrwgO8temB94d+zM/05bBKq1kkQReBna9uOZM1ir3U=; b=Y9E/d5h02kqkUtcxlLVnUvsukmYXItQkMlUfc4idZYBztitJZrFt1lmMteYUnGd/Bp Cun3FNZ0IFTCfmbRdE3jwXX7SgTklXXp4vmc5+eEi8K9QPCZBRsKBOSA2lCOHiUfnktL 1+v0aE27/SK/ar1TqGxCY5oi+lx6iNoppixJ01rVJgLPfVHzLyzMHgkSB322nGXM0iJW RIJSaKShYkVTQZl+MHtLQLKaY73At/Ih5Z/9F6JfN11NpwQwZZXXgpd+V1eVZEwa7D/W 1C0/uDwYdAI8b1Wa52I/E6LqwzG1snwI/y387L+sVWcp5Zf4vv3HP3XobRXijfaSHg4+ KgDA== X-Gm-Message-State: AOJu0YwXRYwiiNRKFmYaChgBerIvSNy8EaSp/nLgiO9Mg9Y3bvkJBLIN 5FxqWjvu/q3/2FmTwpvlvN3XYwvOjAKyY0VW2kx1MAOwXJ1jlWhOoks= X-Google-Smtp-Source: AGHT+IFfDhk1oqlGyM4XybwSmuS53fl4Z/hCMpdRN7HIWB3OTgv5FmSP8FFs0GPXUfL5I+zcd86cJWfCQigUtFHV+zs= X-Received: by 2002:a17:906:5c:b0:9a5:db06:4264 with SMTP id 28-20020a170906005c00b009a5db064264mr3873446ejg.72.1694075312795; Thu, 07 Sep 2023 01:28:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dave Page Date: Thu, 7 Sep 2023 09:28:20 +0100 Message-ID: Subject: Re: Birmingham City Council chose Oracle, went broke because of it ;) To: Magnus Hagander Cc: Justin Clift , PostgreSQL Advocacy Content-Type: multipart/alternative; boundary="0000000000003e0b3f0604c0a503" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003e0b3f0604c0a503 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 7 Sept 2023 at 09:23, Magnus Hagander wrote: > On Thu, Sep 7, 2023 at 1:49=E2=80=AFAM Justin Clift wrote: > > > > Heh Heh Heh. This is pretty funny: > > > > > https://www.theregister.com/2023/09/05/birmingham_city_council_oracle/ > > > > "Birmingham City Council, the largest local authority in Europe, has > > declared itself in financial distress after troubled Oracle project > > costs ballooned from =C2=A320 million to around =C2=A3100 million (= $125.5 > > million)." > > > > Wonder if they'll make the smart choice next time around, and choose PG > > + a decent vendor instead? :) > > In fairness, that project is about Oracle Fusion, not the database. So > PG doesn't have a competing product. There are opensource ERP products > out there, but I'm not sure they're advanced enough to handle > something like that... > Indeed. It also only amounts for a fraction of the council's liabilities. The vast majority is from an equal pay judgement against them, which iirc, totals a couple of billion pounds (of which they've paid off over half in the last decade I believe). So, yeah, the Oracle thing is a massive screw up. But it's not what caused the majority of their problems. --=20 Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org EDB: https://www.enterprisedb.com PGDay UK 2023, September 12, London: https://2023.pgday.uk --0000000000003e0b3f0604c0a503 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, 7 Sept 2023 at 09:23, Magnus = Hagander <magnus@hagander.net= > wrote:
On Thu, Sep 7, 2023 at 1:49=E2=80=AFA= M Justin Clift <justin@postgresql.org> wrote:
>
> Heh Heh Heh.=C2=A0 This is pretty funny:
>
>=C2=A0 =C2=A0 https://www.= theregister.com/2023/09/05/birmingham_city_council_oracle/
>
>=C2=A0 =C2=A0 "Birmingham City Council, the largest local authorit= y in Europe, has
>=C2=A0 =C2=A0 =C2=A0declared itself in financial distress after trouble= d Oracle project
>=C2=A0 =C2=A0 =C2=A0costs ballooned from =C2=A320 million to around =C2= =A3100 million ($125.5
> million)."
>
> Wonder if they'll make the smart choice next time around, and choo= se PG
> + a decent vendor instead? :)

In fairness, that project is about Oracle Fusion, not the database. So
PG doesn't have a competing product. There are opensource ERP products<= br> out there, but I'm not sure they're advanced enough to handle
something like that...

Indeed. It also = only amounts for a fraction of the council's liabilities. The vast majo= rity is from an equal pay judgement against them, which iirc, totals a coup= le of billion pounds (of which they've paid off over half in the last d= ecade I believe).

So, yeah, the Oracle thing is a = massive screw up. But it's not what caused the majority of their proble= ms.
=C2=A0
-- <= /span>
Dave = Page
PostgreSQL: https://www.postgresql.org

PGDay UK 2023, September 12, London: https://2023.pgday.uk

--0000000000003e0b3f0604c0a503--