Request a Demo
Home   >   mailing lists

Re: Add sanity check for duplicate enum values in GUC definitions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Add sanity check for duplicate enum values in GUC definitions
Date
Msg-id c0584af9-37b9-4ab1-bdfa-d7e52e3d8aba@eisentraut.org
Whole thread Raw
In response to Add sanity check for duplicate enum values in GUC definitions  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: Add sanity check for duplicate enum values in GUC definitions
List pgsql-hackers
Tree view 
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?

pgsql-hackers by date:

Previous
From: Jasper Smit
Date:
Subject: Re: Visibility bug in tuple lock
Next
From: Andres Freund
Date:
Subject: Re: Buffer locking is special (hints, checksums, AIO writes)