| From: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Operation log for major operations |
| Date: | 2022-12-05 08:11:51 |
| Message-ID: | 066b68a1-6e25-6e10-a88f-4f24e7b60a51@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
>I think storing this in pg_control is a bad idea. That file is
>extremely critical and if you break it, you're pretty much SOL on
>recovering your data. I suggest that this should use a separate file.
Thanks. Operation log location changed to 'global/pg_control_log' (if
the name is not pretty, it can be changed).
I attached the patch (v2-0001-Operation-log.patch) and description of
operation log (Operation-log.txt).
With best regards,
Dmitry Koval
Postgres Professional: http://postgrespro.com
| Attachment | Content-Type | Size |
|---|---|---|
| Operation-log.txt | text/plain | 8.7 KB |
| v2-0001-Operation-log.patch | text/plain | 47.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-12-05 08:16:56 | Re: Generate pg_stat_get_* functions with Macros |
| Previous Message | Drouvot, Bertrand | 2022-12-05 08:11:43 | Re: Generate pg_stat_get_* functions with Macros |