# Postgres ENUM support for Ash.Type.Enum?

**URL:** <https://forum.elixirforum.com/t/postgres-enum-support-for-ash-type-enum/73850>\
**Category:** Questions\
**Tags:** ash, ash-postgres\
**Created:** [January 1, 2026, 9:32pm UTC](https://forum.elixirforum.com/t/postgres-enum-support-for-ash-type-enum/73850 "2026-01-01T21:32:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sezaru](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/sezaru/32/36113_2.png) [@sezaru](https://forum.elixirforum.com/u/sezaru)\
**Post date:** [January 2, 2026, 1:48am UTC](https://forum.elixirforum.com/t/postgres-enum-support-for-ash-type-enum/73850/3 "2026-01-02T01:48:31Z")

</div>

It has, but that became an issue if you have a huge table with a bunch of enums since that will increase the size of the table a lot. At the same time I don’t want to use integers since it decreases readability when querying the DB directly.

AFAIK, that annoying part was more prevalent before Postgres 9 since it could only add new values to the end of the enum. after that you can add in any position.

Also, needing a migration to add/remove values can be seen as something annoying, but it can also be seen as a advantage since it makes sure that no one can add wrong data to it.

---

_[View the full topic](https://forum.elixirforum.com/t/postgres-enum-support-for-ash-type-enum/73850)._