Postgres Pro
Downloads
Home   >   mailing lists

Re: Operation log for major operations - Mailing list pgsql-hackers

From Dmitry Koval
Subject Re: Operation log for major operations
Date
Msg-id 066b68a1-6e25-6e10-a88f-4f24e7b60a51@postgrespro.ru
Whole thread Raw
In response to Re: Operation log for major operations  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Operation log for major operations  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Generate pg_stat_get_* functions with Macros
Next
From: Michael Paquier
Date:
Subject: Re: Generate pg_stat_get_* functions with Macros