| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Greg Smith <gsmith(at)gregsmith(dot)com> |
| Subject: | Re: Enabling Checksums |
| Date: | 2012-11-09 18:58:57 |
| Message-ID: | 1352487537.6292.80.camel@jdavis-laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2012-11-08 at 23:33 -0300, Alvaro Herrera wrote:
> There's no such thing as a system-wide VACUUM. The most you can get is
> a database-wide VACUUM, which means you'd have to store the state
> per-database somewhere (presumably the pg_database catalog), and perhaps
> pg_control could have it as a system-wide value that's computed as the
> minimum of all database states (so it stays "enabling" until all
> databases have upgraded to "on").
That's a good point. Maybe this should be done as an offline operation
using a command-line utility?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2012-11-09 19:48:12 | Re: Enabling Checksums |
| Previous Message | Jeff Davis | 2012-11-09 18:53:38 | Re: Enabling Checksums |