Matouš Jan Fialka

Maybe a stupid idea but what about to implement some log sampling like, for example, ```ini log-level-sample-file=detail=0.001,info=0.01,warning=0.1 ``` or, perhaps, ```ini log-level-sample-file=detail=1000,info=100,warning=10 ``` or, maybe, ```ini log-level-sample-file-detail=1000 log-level-sample-file-info=100 log-level-sample-file-warning=10 ```...

Can it be just toggled on and off using JS, like in [this one formatter](https://github.com/zeroturnaround/sql-formatter)?

Hello. What about to let users to choose between: 1. a generated **guess-proof** identifier (UUID or something similar), 2. some custom identifier (if there is no collision with already existing...

@nikkhils That's great! Thank you.

Hi @nikkhils do you have any news about this, please?

@nikkhils, @svenklemm, @cevian Hi guys, any update on this, please?

This is very nice resource for comparison between major versions: [PgStats](https://pgstats.dev/).

Please, remove UTF-8 drawing characters (and other weird characters) from literary everywhere in configuration and either replace them with ASCII `+-|` if you insist on the borders, line, frames etc....

@Vonng Does this mean you aim to implement some sort of periodic scheduler (eg. Cron-like)? If so, it would be nice if the implementation also supported `@daily`, `@hourly`, `@weekly`, `@montly`,...

@sosedoff Sorry for the delay. Many tables per schema (normalized database; TimescaleDB with Promscale ingesting Telegraf measures via Prometheus remote write protocol or something similar to this could be a...