Re: Composite type storage overhead - Mailing list pgsql-general

From Michael Lewis
Subject Re: Composite type storage overhead
Date
Msg-id CAHOFxGqhV-womDiquSgVYw5o8WEsGU1UcfYbT4wUViMfbJ_--Q@mail.gmail.com
Whole thread Raw
In response to Re: Composite type storage overhead  (Laiszner Tamás <t.laiszner@outlook.com>)
List pgsql-general
On Thu, Oct 24, 2019 at 3:35 AM Laiszner Tamás <t.laiszner@outlook.com> wrote:

Thanks for the suggestion to split up the primary key into components. But even going down this way, packing the components into one superstructure (composite type) would be beneficial as the same scheme is used across multiple tables. And we are back at the original problem.


This is probably a completely naive question, but why not store this in a text field?

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Quere keep using temporary files
Next
From: Alexander Farber
Date:
Subject: Re: Trying to fetch records only if preceded by at least another one