Re: making an unlogged table logged
От | Robert Haas |
---|---|
Тема | Re: making an unlogged table logged |
Дата | |
Msg-id | AANLkTimf_NxQma7tB4MFhrhtW-=rVwk5x6arPk8Bvap0@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: making an unlogged table logged (Rob Wultsch <wultsch@gmail.com>) |
Ответы |
Re: making an unlogged table logged
|
Список | pgsql-hackers |
On Tue, Jan 4, 2011 at 10:56 PM, Rob Wultsch <wultsch@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
В списке pgsql-hackers по дате отправления: