From: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Operation log for major operations |
Date: | 2022-11-21 13:55:36 |
Message-ID: | 30979c9c-b804-d346-18d5-2e3ff26a9055@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks for references, Justin!
Couple comments about these references.
1) "Make unlogged table resets detectable".
https://www.postgresql.org/message-id/flat/62750df5b126e1d8ee039a79ef3cc64ac3d47cd5.camel%40j-davis.com
This conversation is about specific problem (unlogged table repairing).
Operation log has another use - it is primary a helper for diagnostics.
2) "RFC: Add 'taint' field to pg_control."
https://www.postgresql.org/message-id/flat/20180228214311.jclah37cwh572t2c%40alap3.anarazel.de
This is almost the same problem that we want to solve with operation
log. Differences between the operation log and what is discussed in the
thread:
* there suggested to store operation log in pg_control file - but
separate from pg_control main data (and write data separately too);
* operation log data can be represented in relational form (not flags),
this is more usable for RDBMS;
* number of registered event types can be increased easy (without
changes of storage).
--
With best regards,
Dmitry Koval
Postgres Professional: http://postgrespro.com
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2022-11-21 14:07:17 | Re: createuser doesn't tell default settings for some options |
Previous Message | Dagfinn Ilmari Mannsåker | 2022-11-21 13:42:25 | Re: TAP output format in pg_regress |