Re: Best Practices for Extensions, limitations and recommended use for monitoring

Hi Tom, > Am 14.08.2018 um 17:07 schrieb Tom Lane : > > I'd say that's generally deprecated. Per the documentation, you can write > CREATE USER commands in an extension script if you like, but the roles > won't be considered to "belong" to the extension, and won't be dropped > when it is. This

Best Practices for Extensions, limitations and recommended use for monitoring

://github.com/alvar-freude/Posemo) The Posemo framework creates for each check a PostgreSQL function with the SECURITY DEFINER option, which can (only) be called by an unprivileged user, who only can call the functions and don’t need access to any data, system table etc. A simple alive check looks like

Re: Question about buffers_alloc in pg_stat_bgwriter view for monitoring

Hi, > Am 29.03.2018 um 10:30 schrieb Gunnar Nick Bluth : > > Thus, buffer_alloc is the global count of buffers allocated in the > cluster. That it appears in the bgwriter statistics is more or less > coincidental. But it seems not to be the total shared_buffers used, but the total number of all

Question about buffers_alloc in pg_stat_bgwriter view for monitoring

monitoring framework (https://github.com/alvar-freude/Posemo) and now look how to make reasonable checks (and as result graphs) for BGWriter activity. At the moment my plan is to make more then one check out of pg_stat_bgwriter: * BGWriterAmount A check which returns the amount of written data