While there are some docs on it, I decided to write about it, in perhaps more accessible language - not as a developer, but as PostgreSQL user. Some parts (quite large parts) were described in one of my earlier posts, but ...
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 ...
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 ...
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 :)
