Hello > >> > Does it make sense to store this information in pg_control? That doesn't >> > require adding any new file, and it has the benefit that it's already >> > checksummed. It's available during recovery and can be made available >> > pretty easily in the places where we write data. >> > >> > And the next question is what commands to add to change state. Ideas: >> > >> > CHECKSUMS ENABLE; -- set state to "Enabling" >> > CHECKSUMS DISABLE; -- set state to "Off" >> >> Don't like this, please make it a GUC. > > I'll see if you have ideas about how to resolve the problems with a GUC > that I mentioned above. But if not, then what about using a utility, > perhaps called pg_checksums? That way we wouldn't need new syntax.
I don't think so GUC are good for this purpouse, but I don't like single purpouse statements too. what do you think about enhancing ALTER DATABASE statement some like ALTER DATABASE name ENABLE CHECKSUMS and ALTER DATABASE name DISABLE CHECKSUMS Regards Pavel -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
