Opinion: domains are useful if you give them names that are full of meaning. For example if you have the same type of data accross tables "item_number" or "account" etc so that you can use them to describe what you want stored in them and ensure the same defaults, nulls etc are applied accross tables. Having randomly named or encoded lists just makes life more complicated.
On Wed, 20 Aug 2025, 18:13 Greg Sabino Mullane, <htamfids@xxxxxxxxx> wrote:
On Wed, Aug 20, 2025 at 12:48 AM Ertan Küçükoglu <ertan.kucukoglu@xxxxxxxxx> wrote:Does the second table have any technical advantage/disadvantage over plain data type definition?Less metadata in memory? High metadata in memory? Less/increased disk space?Same disk space. No disadvantage other than confusing your users, and any performance differences will be so minor as to be unmeasurable. (my two cents: domains are best when the data type is complex AND shared across multiple tables. Even then I tend to avoid them.)Cheers,Greg--Crunchy Data - https://www.crunchydata.comEnterprise Postgres Software Products & Tech Support
