Forum > Other

StackOverflow 2022 Developer Survey

(1/2) > >>

avra:
https://survey.stackoverflow.co/2022/#technology-most-popular-technologies

It was commented on Marco Cantu's blog:
https://blog.marcocantu.com/blog/2022-june-delphi-stackoverflow-survey.html

Please look at it just as an interesting to read survey stats, and not like a reason for another passionate anti TIOBE like flame war.

For me, regarding databases the most interesting part was that PostgreSQL was number 1 choice for professional developers (pleasant surprise), and that InfluxDB was not on the list at all (unpleasant surprise).

PierceNg:

--- Quote from: avra on July 11, 2022, 11:11:51 am ---For me, regarding databases the most interesting part was that PostgreSQL was number 1 choice for professional developers (pleasant surprise), and that InfluxDB was not on the list at all (unpleasant surprise).

--- End quote ---

For monitoring I run the TIG stack: Telegraf, InfluxDB and Grafana. When the time comes to reinstall, I'll most likely migrate from InfluxDB to some time series DB extension for PostgreSQL. The advantages are familiarity and size of the PostgreSQL ecosystem.

Marc:

--- Quote from: avra on July 11, 2022, 09:07:05 pm ---
--- Quote from: PierceNg on July 11, 2022, 01:42:25 pm ---I'll most likely migrate from InfluxDB to some time series DB extension for PostgreSQL.
--- End quote ---
My use case benefits from being able to set InfluxDB data to automatically expire after some time period (like 1 year). PostgreSQL can not do that and I would have to schedule some long SQL query and use CPU intensively while executing that query. InfluxDB simply deletes the file with old data and continues without interruption and extensive CPU load.

--- End quote ---

In PostgreSQL, if you partition your table on a time range you can drop a partition instantaneously. If you set the range for instance on a day, you can drop your data for given day without heavy queries, with little to no overhead

avra:

--- Quote from: Marc on July 12, 2022, 10:28:40 am ---In PostgreSQL, if you partition your table on a time range you can drop a partition instantaneously. If you set the range for instance on a day, you can drop your data for given day without heavy queries, with little to no overhead
--- End quote ---
Thanks Marc for this correction. I was not aware of that. According to documentation, you would steel need to manually drop or add date range partitions with PostgreSQL. However it seams to be much faster then bulk delete so it could be useful in some use cases.

Marc:

--- Quote from: avra on July 12, 2022, 01:32:16 pm ---Thanks Marc for this correction. I was not aware of that.

--- End quote ---
I can imagine. At the time this got introduced, we just had finished our own solution with daily tables  :(

--- Quote ---According to documentation, you would steel need to manually drop or add date range partitions with PostgreSQL.
--- End quote ---
There exist a package which can handle the auto add and drop. OTOH, if you have some job running which drops a partition every month, the same job can add a new month

Navigation

[0] Message Index

[#] Next page

Go to full version