| From: | Justin Clift <justin(at)postgresql(dot)org> |
|---|---|
| To: | Jacob Champion <jchampion(at)timescale(dot)com> |
| Cc: | pgsql-advocacy(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Timescale's State of PostgreSQL 2023 Survey |
| Date: | 2023-08-03 21:21:40 |
| Message-ID: | d38a8fb66ee1a51146297ed1866a2b9e@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Adlersburg | 2023-08-04 09:54:05 | Re: Timescale's State of PostgreSQL 2023 Survey |
| Previous Message | Jacob Champion | 2023-08-01 18:59:39 | Timescale's State of PostgreSQL 2023 Survey |