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 <pgsql-advocacy-owner+archive@lists.postgresql.org>)
	id 1qRfla-002ZUZ-8k
	for pgsql-advocacy@arkaria.postgresql.org; Thu, 03 Aug 2023 21:21:54 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-advocacy-owner+archive@lists.postgresql.org>)
	id 1qRflY-00HUAg-HN
	for pgsql-advocacy@arkaria.postgresql.org; Thu, 03 Aug 2023 21:21:52 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <justin@postgresql.org>)
	id 1qRflY-00HUAY-AN
	for pgsql-advocacy@lists.postgresql.org; Thu, 03 Aug 2023 21:21:52 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <justin@postgresql.org>)
	id 1qRflQ-000PhX-8g
	for pgsql-advocacy@lists.postgresql.org; Thu, 03 Aug 2023 21:21:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type:
	Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender
	:Reply-To:Content-ID:Content-Description;
	bh=odDRZUWISpncYPn7pOK5jGgXCkIwEd3LqLrWnsmyOgg=; b=mmRZ06Vx/NBLO3frgJ4KSBAeid
	cgOZztvbPv4otBd2gBDPZGopYbZBWS+FIKlWNVbrGce+0OamieiWey7uu4AdrDE2puOkE0jLpCg7o
	vyoe7XOYucc2CQqd3FpnDPrizEqryME5oBagwQaLSmzcADVGS6274xVsv1i4kksGm63BV/fKEiub2
	7s6fdIv4LUa++rZ3hZGLR0CofC90LwguGYgG6tLHsqYpyo9GfZF0urOzfruww8TV8+G64grmzOotY
	IomfjVKQbfI2AW/sWsILCvQftjF/mRFq7lAtPi5ARnwSuIA5rhV7nXUs+HCa3I92zxH4jjpOYRlrA
	QIQToDJA==;
Received: from meldrar.postgresql.org ([87.238.57.231]
 helo=webmail.postgresql.org)
	by meldrar.postgresql.org with esmtpsa  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <justin@postgresql.org>)
	id 1qRflN-000w3K-5v; Thu, 03 Aug 2023 21:21:43 +0000
MIME-Version: 1.0
Date: Fri, 04 Aug 2023 07:21:40 +1000
From: Justin Clift <justin@postgresql.org>
To: Jacob Champion <jchampion@timescale.com>
Cc: pgsql-advocacy@lists.postgresql.org
Subject: Re: Timescale's State of PostgreSQL 2023 Survey
In-Reply-To: <e3606c65-1f57-ee7e-12c3-36d90377e58b@timescale.com>
References: <e3606c65-1f57-ee7e-12c3-36d90377e58b@timescale.com>
User-Agent: Roundcube Webmail/1.4.13
Message-ID: <d38a8fb66ee1a51146297ed1866a2b9e@postgresql.org>
X-Sender: justin@postgresql.org
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-advocacy.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-advocacy@lists.postgresql.org>
List-Owner: <mailto:pgsql-advocacy-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-advocacy>
Archived-At: 
 <https://www.postgresql.org/message-id/d38a8fb66ee1a51146297ed1866a2b9e%40postgresql.org>
Precedence: bulk

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
<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...  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