From: | Seamus Abshere <seamus(at)abshere(dot)net> |
---|---|
To: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: "Shared strings"-style table |
Date: | 2017-10-13 16:43:52 |
Message-ID: | 1507913032.1218209.1137930856.7E2526E3@webmail.messagingengine.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2017-10-13 16:52:06 | Re: "Shared strings"-style table |
Previous Message | Peter Geoghegan | 2017-10-13 16:43:28 | Re: Merge - Insert Select |