Re: Add sanity check for duplicate enum values in GUC definitions

On 15.12.25 10:16, Chao Li wrote:
> The motivation for this patch comes from my own experience. While 
> working on [1]. I added an enum-typed GUC and made a copy-and-paste 
> mistake, assigning the same numeric value to two different enum entries. 
> This resulted in confusing runtime behavior and cost me about an hour to 
> track down.

Why do you assign explicit values at all?