Re: vacuum_truncate configuration parameter and isset_offset

The argument being made is that the enum patch adheres to established practices; and when adding new code that new code is encouraged to adhere to how existing code is written.  A vote to keep to such guidelines seems reasonable and sufficient; and can outweigh quite a bit of deficiency such existing code may have relative to the new proposal.  The burden is on the new code to justify why it should violate established conventions.

So, the question posed is should the new way of doing this, established by the committed patch, be allowed to stay and exist side-by-side with the original convention for handling the determination of whether an option is set? I’m +.75 for no and +.25 for yes.  Convention tips the balance for me.

David J.