Re: BUG #10675: alter database set tablespace and unlogged table

Looks like there is no agreement on this. I agree with Andreas that given the current mechanism of truncating unlogged relations at the end of redo recovery, there is no danger in not flushing the dirty buffers belonging to unlogged relation at a normal checkpoint. Having said that, I find it confusing that we don't do that, for one reason that Tom explained and also because there is practically just no way to flush those dirty buffers to disk if the user wants so. 

Also, there had been discussions about altering unlogged tables to normal tables and we may also want to improve upon the current mechanism of truncating unlogged relations at the end of recovery even if the table was fully synced to the disk. It looks simpler to just flush everything instead of devising a new flag for checkpoint.

 

Anyone else has an opinion on this?