David, On Mon, Apr 20, 2026 at 9:32 PM David G. Johnston <[email protected]> wrote: > > On Monday, April 20, 2026, Igor Korot <[email protected]> wrote: >> >> Hi, everybody, >> >> On Mon, Apr 20, 2026 at 8:29 PM David G. Johnston >> <[email protected]> wrote: >> > >> > On Mon, Apr 20, 2026 at 7:47 PM Igor Korot <[email protected]> wrote: >> >> >> >> My understanding is that if I have 3 "BIG5" encodings, only one can be >> >> a default. >> > >> > >> > That would be a misunderstanding of what a conversion table is about. >> >> What I did: >> >> 1. Google "PostgreSQL create database" >> 2. Click the first link - to PostgreSQL documentation. >> 3. The command have many options. One of them is "Encoding". >> 4, Scrolled down for an explanation. The explanation had a link. >> 5. Clicked the link. Received a page with the list of encodings. >> >> At this point I asked the original question >> Does the list on that page stored somewhere? Or it is hardcoded inside >> the sources? >> >> That's when I started receiving a references to that table. >> >> Did I ask the wrong question? > > > And the answer you got was “no, it’s not (i.e., it’s hardcoded inside), but > you can get to it indirectly”. In this case if you involve the pgconversion > table you should ignore the conversion is default field as it has nothing to > do with the question - what encodings does the system recognize. You also > got an answer involving generate_series.
Understood, thx. This clears it up. Sorry for the confusion. And yes - I will query the pg_conversion table. Thx once again. > > David J. >
