On Tue, Jan 4, 2011 at 10:56 PM, Rob Wultsch <wult...@gmail.com> wrote: > 1. Could the making a table logged be a non-exclusive lock if the > ALTER is allowed to take a full checkpoint?
No, that doesn't solve either of the two problems I described, unfortunately. > 2. Unlogged to logged has giant use case. Agree. > 3. In MySQL I have had to ALTER tables to engine BLACKHOLE because > they held data that was not vital, but the server was out of IO. Going > logged -> unlogged has a significant placed, I think. Interesting. So you'd change a logged table into an unlogged table to cut down on I/O, and take the risk of losing the data if the server went down? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
