| From: | Seamus Abshere <seamus(at)abshere(dot)net> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: "Shared strings"-style table |
| Date: | 2017-10-13 19:08:57 |
| Message-ID: | 1507921737.3559508.1138074208.021B93EC@webmail.messagingengine.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Oct 13, 2017, at 03:16 PM, David G. Johnston wrote:
> implement a "system-managed-enum" type with many of the same properties
[...]
> TOAST does involved compression but the input to
> the compression algorithm is a single cell (row and column) in a table.
> As noted above I consider the TOAST table and main table to be a single
> logical table.
See this sounds like _exactly_ what I want. Except with a content hash
instead of an id.
Seems to me like all of the machinery that allows you to look things up
by TOASTed columns and subsequently return TOASTed values as if they
resided in the same physical table is what is needed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igal @ Lucee.org | 2017-10-13 19:09:40 | Re: Permissions for Web App |
| Previous Message | Thomas Kellerer | 2017-10-13 19:03:10 | Re: "Shared strings"-style table |