|From:||Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>|
|To:||Nicky Larson <said(dot)assemlal(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: Contribution to postgresql|
|Views:||Raw Message | Whole Thread | Download mbox|
Nicky Larson wrote:
> I am using postgresql at work, and I would like to contribute.
> From the todo list, I chose:
> Allow log_min_messages to be specified on a per-module basis
> Is this feature always wanted ? That would be my first contribution to postgresql, is it an easy one ?
I guess the difficult part might be specifying what exactly the
feature does and reaching a consensus on that.
TODO list items have the tendency to be tricky that way - things
that are easy to design are often already implemented.
Currently you can set the parameter based on user and database
(ALTER ROLE/DATABASE SET log_min_messages = ...).
One idea would be to enable a setting only for a certain value
of "application_name". That could be done with an additional clause
to ALTER ROLE and ALTER DATABASE. How you could do that for a global
setting is unclear to me; surely you wouldn't change the syntax in
One good road to get into PostgreSQL development is by reviewing patches.
That allows you to learn from others and get to know parts of the code
you are not yet familiar with.
There is always a shortage of reviewers!
|Next Message||Masahiko Sawada||2018-10-22 10:35:04||Re: [HACKERS] Restricting maximum keep segments by repslots|
|Previous Message||Andrey Borodin||2018-10-22 10:11:25||Re: [Patch] pg_rewind: options to use restore_command from recovery.conf or command line|