Settings and activity
24 results found
-
6 votes
Felix Wu supported this idea ·
An error occurred while saving the comment -
5 votes
-
56 votes
-
10 votes
-
5 votes
-
2 votes
-
41 votes
-
6 votes
Although this sounds reasonable in practice and many Linux distributions follow this, the projects we run at Aiven do not. So we are unable to build secured versions of open-source projects for long-term support. This would require an immense amount of engineering to maintain legacy versions of these 11 open-source projects. We also run Linux infrastructure, which is not part of the LTS model, so this would be yet another issue with the idea of LTS. If you'd like to discuss more, I am happy to speak with you.
-
9 votes
An error occurred while saving the comment I have a customer calling this API:
https://api.aiven.io/v1/account/*******/authenticationGetting the following without any details on the actual error:
HTTP/1.1 500 Internal Server Error
{"message":"Internal Server Error"} -
2 votes
An error occurred while saving the comment defaultdb=> CREATE EXTENSION pg_stat_statements;
CREATE EXTENSIONdefaultdb=> SELECT * FROM pg_settings WHERE name LIKE 'pg_stat_statements%';
name | setting | unit | category | short_desc | extra_desc | context | vartype | source | min_val | max_val | enumvals | boot_val | reset_val | sourcefile | sourceline | pending_restart
-----------------------------------+---------+------+--------------------+----------------------------------------------------------------------+------------+------------+---------+---------+---------+------------+----------------+----------+-----------+------------+------------+-----------------
pg_stat_statements.max | 5000 | | Customized Options | Sets the maximum number of statements tracked by pg_stat_statements. | | postmaster | integer | default | 100 | 1073741823 | | 5000 | 5000 | | | f
pg_stat_statements.save | on | | Customized Options | Save pg_stat_statements statistics across server shutdowns. | | sighup | bool | default | | | | on | on | | | f
pg_stat_statements.track | top | | Customized Options | Selects which statements are tracked by pg_stat_statements. | | superuser | enum | default | | | {none,top,all} | top | top | | | f
pg_stat_statements.track_planning | off | | Customized Options | Selects whether planning duration is tracked by pg_stat_statements. | | superuser | bool | default | | | | off | off | | | f
pg_stat_statements.track_utility | on | | Customized Options | Selects whether utility commands are tracked by pg_stat_statements. | | superuser | bool | default | | | | on | on | | | f
(5 rows) -
6 votes
An error occurred while saving the comment This is a must have for my customer.
-
13 votes
-
14 votes
-
20 votes
-
8 votes
-
8 votes
An error occurred while saving the comment GitHub - https://github.com/hydradatabase/hydra
Apache-2.0 license - https://github.com/hydradatabase/hydra/blob/main/LICENSE
https://www.hydra.so/ -
24 votes
-
6 votes
-
10 votes
-
52 votes
As PG developer,
I want to use this new feature in pgbocuner 1.22.0
"support for the DISCARD ALL and DEALLOCATE ALL commands when enabling prepared statement support in transaction pooling mode (by setting max_prepared_statements to a non-zero value). This is an important improvement in the prepared statement support that clears the road for us to be able to enable prepared statement support by default in a future release."
https://www.pgbouncer.org/2024/01/pgbouncer-1-22-0