Re: [GENERAL] "Shared strings"-style table
От | Seamus Abshere |
---|---|
Тема | Re: [GENERAL] "Shared strings"-style table |
Дата | |
Msg-id | 1507913032.1218209.1137930856.7E2526E3@webmail.messagingengine.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] "Shared strings"-style table (Melvin Davidson <melvin6925@gmail.com>) |
Ответы |
Re: [GENERAL] "Shared strings"-style table
Re: [GENERAL] "Shared strings"-style table |
Список | pgsql-general |
> > On Fri, Oct 13, 2017 at 8:49 AM, Seamus Abshere wrote: > >> Theoretically / blue sky, could there be a table or column type that > >> transparently handles "shared strings" like this, reducing size on disk > >> at the cost of lookup overhead for all queries? > >> (I guess maybe it's like TOAST, but content-hashed and de-duped and not > >> only for large objects?) On Fri, Oct 13, 2017, at 01:29 PM, Melvin Davidson wrote: > What was described is exactly what relations and Foreign Keys are for. hi Melvin, appreciate the reminder. Our issue is that we have 300+ columns and frequently include them in the SELECT or WHERE clauses... so traditional normalization would involve hundreds of joins. That's why I ask about a new table or column type that handles basic translation and de-duping transparently, keeping the coded values in-table. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: