For todays post in Understanding postgresql.conf series, I chose work_mem parameter.
Starting new blog series – explanation of various configuration parameters.
I will of course follow no schedule or order – if I'd had to – it would be my job, and in this way – it's fun.
First configuration parameter to write about is checkpoint_completion_target.
On 28th of November Tom Lane committed patch by Dave Page, which adds new capability to system monitoring and logging:
Log Message: ----------- Add support for an application_name parameter, which is displayed in pg_stat_activity and recorded in log entries. Dave Page, reviewed by Andres Freund
On 7th of October Alvaro Herrera committed his own patch, which adds quite interesting possibilty:
Log Message: ----------- Make it possibly TO specify GUC params per USER AND per DATABASE. CREATE a NEW catalog pg_db_role_setting WHERE they are now stored, AND better encapsulate the code that deals WITH settings INTO its realm. The OLD datconfig AND rolconfig COLUMNS are removed. psql has gained a \drds command TO display the settings. Backwards compatibility warning: while the backwards-compatible system views still have the config COLUMNS, they no longer completely represent the configuration FOR a USER OR DATABASE. Catalog version bumped.
On 19th of November Tom Lane committed patch by Takahiro Itagaki which does:
Add auto-explain contrib module for automatic logging of the plans of slow-running queries.
Today another two new additions to PostgreSQL – as You can see may commit-fest seems to work pretty good 🙂