Enabling CSV logging on PostgreSQL

Production Change - Criticality 1 C1

Change Objective	Describe the objective of the change
Change Type	ConfigurationChange
Services Impacted	PostgreSQL
Change Team Members	Name of the engineers involved in the change
Change Severity	C1
Change Reviewer	Ongres (?)
Tested in staging	Evidence or assertion the change was tested on staging environment
Dry-run output	If the change is done through a script, it is mandatory to have a dry-run capability in the script, run the change in dry-run mode and output the result
Due Date	Date and time in UTC timezone for the execution of the change, if possible add the local timezone of the engineer executing the change
Time tracking	To estimate and record times associated with changes ( including a possible rollback )
Downtime Component	if yes how many minutes

Detailed steps for the change

https://ops.gitlab.net/gitlab-cookbooks/chef-repo/-/merge_requests/2705 has an example change. We need to set the following option:

        "log_destination": "csvlog"

PostgreSQL will NOT need to be restarted for this to work. The FluentD changes to parse the CSV logs has already been deployed.

Rollback steps

Remove those entries.

Changes checklist

• Detailed steps and rollback steps have been filled prior to commencing work
• Person on-call has been informed prior to change being rolled out