| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Ertan Küçükoglu <ertan(dot)kucukoglu(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Domains vs data types |
| Date: | 2025-08-20 16:12:25 |
| Message-ID: | CAKAnmmJfh2hPk8v597tRNVhM9_4oCQmTtJ6CVqHAp4hO0qPj6Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 20, 2025 at 12:48 AM Ertan Küçükoglu <ertan(dot)kucukoglu(at)gmail(dot)com>
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.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2025-08-20 16:26:19 | Re: vacuum analyze query performance - help me understand |
| Previous Message | hubert depesz lubaczewski | 2025-08-20 16:08:11 | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |