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 1qRrVm-003Peq-6f for pgsql-advocacy@arkaria.postgresql.org; Fri, 04 Aug 2023 09:54:22 +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 1qRrVk-0067i8-Gc for pgsql-advocacy@arkaria.postgresql.org; Fri, 04 Aug 2023 09:54:20 +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 1qRrVk-0067i0-9f for pgsql-advocacy@lists.postgresql.org; Fri, 04 Aug 2023 09:54:20 +0000 Received: from mail-yb1-xb30.google.com ([2607:f8b0:4864:20::b30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qRrVi-000Tlx-4A for pgsql-advocacy@lists.postgresql.org; Fri, 04 Aug 2023 09:54:19 +0000 Received: by mail-yb1-xb30.google.com with SMTP id 3f1490d57ef6-d43930354bcso569237276.3 for ; Fri, 04 Aug 2023 02:54:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691142857; x=1691747657; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iYuA3mpsa9OXXalWYUwgq9T/ft5Tg2qBJepCo6o/ZIw=; b=jxXGg3JeRKq0LKMt48eLBr5XPzVIeop7sqzHSU7MFejDnNWhEgp515XEhIMj6ZJeVi 5L85IpardIa7msxFzhQEEaUn8RShB3ISVmnidQr2ZcrhY2wPx3VRG0FHrVrGm5RZ1jdt qunIMBldFa3by/ah1HVxAXxs5W0WCs7buDqFYqRMNsn/epTgzNLocbZlT4GGgh27q0hA 4M12ufj9L66PUAgDlVxCfOyYkU4Dk5CSi1+8dK4S8/EJU72o/zLkPoCK6HPUADulKw6V sdlkk/rSrStMn/RNWFsa8IH1hkwKffXollp3BO189gO9ng32/YXMmkxAMqZ8Cnqg7fO+ arrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691142857; x=1691747657; 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=iYuA3mpsa9OXXalWYUwgq9T/ft5Tg2qBJepCo6o/ZIw=; b=fNQOq3XWUfeiM3oBlBlNQGrs0O+R1CgdNra6c2oL4+T/5pZj3X027VkNfSic2dbZ27 Y/uXlZrZqQOAVDbUvAF0n8SGsm6Y9lB1kekmsvc0lf1V/wJdAsiLaXcACU++vPolNB3F jTv55UcIjgJe1/2AmR2rjRKKu7NmJ0pCKlVNbZuGaZYDDIi+y5Z3B4mbHZIVTe7egeuI KFzocEGVyF9//S08KxCK4HczmbVje2tF/FAlEvKnvRi7TPtWlIyEq/YuiRM0/Y1GR0lN xliQCzowTOEfUWf0K7Et7IXC1VB0B0ZNFNP9oZRO1BWqT4tokKuDdxUOGmHwUBjDEAGN NVaw== X-Gm-Message-State: AOJu0Yw+0Vo8Sq9cJ6FL8QpdGUF0Jwffbt7nqBufrixyxr1T+O1AkC9Q q0mbJUDxdKSznLYD5sbXRLf2pn2i5DRnaEolsio= X-Google-Smtp-Source: AGHT+IGbEK2DJzM9sO8a4qPiPqhPcLdtMweFwtKjnv7ZWE2Kmy6KuL6Uxdp1uii88lT+OUqWcCq5L+k24scGhRhFLp0= X-Received: by 2002:a25:bd7:0:b0:d14:6e28:69a4 with SMTP id 206-20020a250bd7000000b00d146e2869a4mr1381581ybl.29.1691142857232; Fri, 04 Aug 2023 02:54:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Peter Adlersburg Date: Fri, 4 Aug 2023 11:54:05 +0200 Message-ID: Subject: Re: Timescale's State of PostgreSQL 2023 Survey To: Justin Clift Cc: Jacob Champion , pgsql-advocacy@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000004515c3060215e19c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004515c3060215e19c Content-Type: text/plain; charset="UTF-8" Consider selecting 'Other' and writing "all of the above" ;) Justin Clift schrieb am Do., 3. Aug. 2023, 23:21: > On 2023-08-02 04:59, Jacob Champion wrote: > > Hi all! > > > > The State of PostgreSQL 2023 survey is now open! We'd love to hear from > > everyone in the community: > > > > https://tsdb.co/state-of-postgres-2023-survey > > > Just started going through this, but gave up shortly as it seems > to have some fundamental design flaws. :( :( :( > > For example, where it asks what we use PG for at work, it gives > a selection of options... but clicking any one of them wipes out > the others (can't even see them any more). > > It does that with no warning at all, so if (like me) you assumed > it was multiple choice (the only sensible option) then tough luck. > > Looking at the list now, literally all of these are the categories > we use PG for: > > * App Development > * DevOps > * Monitoring > * Real-time Analytics > * SaaS Metrics > * Web analytics > > And that's pretty standard across companies I'd worked at, rather > than this workplace being unusual. > > That was the point I closed the page, as I'm assuming the other > questions probably have similar problems. Obviously could be wrong > though. ;) > > Regards and best wishes, > > Justin Clift > > > --0000000000004515c3060215e19c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Consider selecting 'Other' and writing "all = of the above" ;)

Justin Clift <justin@postgresql.org> schrieb am Do., 3. Aug. 2023, 23:21:
<= /div>
On 2023-08-02 04:59, Jacob Champion wro= te:
> Hi all!
>
> The State of PostgreSQL 2023 survey is now open! We'd love to hear= from
> everyone in the community:
>
>=C2=A0 =C2=A0 =C2=A0https://tsdb.co/stat= e-of-postgres-2023-survey
<snip>

Just started going through this, but gave up shortly as it seems
to have some fundamental design flaws. :( :( :(

For example, where it asks what we use PG for at work, it gives
a selection of options...=C2=A0 but clicking any one of them wipes out
the others (can't even see them any more).

It does that with no warning at all, so if (like me) you assumed
it was multiple choice (the only sensible option) then tough luck.

Looking at the list now, literally all of these are the categories
we use PG for:

=C2=A0 =C2=A0* App Development
=C2=A0 =C2=A0* DevOps
=C2=A0 =C2=A0* Monitoring
=C2=A0 =C2=A0* Real-time Analytics
=C2=A0 =C2=A0* SaaS Metrics
=C2=A0 =C2=A0* Web analytics

And that's pretty standard across companies I'd worked at, rather than this workplace being unusual.

That was the point I closed the page, as I'm assuming the other
questions probably have similar problems.=C2=A0 Obviously could be wrong though. ;)

Regards and best wishes,

Justin Clift


--0000000000004515c3060215e19c--