Re: CHECKPOINT unlogged data

Re: Nathan Bossart
> I broke this up into several small patches.  Notable changes are as
> follows:
> 
> * Adjusted to the tab completion code to work more like the VACUUM utility
>   options.
> 
> * Introduced a new ExecCheckpoint() function in checkpointer.c and moved
>   the privilege check and options parsing there.

Ack. I was pondering if the code was growing too big there, but didn't
want to change too many things at once.

> * Removed the notes in the docs about when to use the CHECKPOINT command.
>   I'm not opposed to adding something like that (in fact, I think it's a
>   good idea), but IMHO we should bikeshed on that separately, maybe even in
>   a new thread.

I would have thought this already happened here. 

> Thoughts?

Fine with me, thanks!

Christoph