Postgres Pro
Downloads
Home   >   mailing lists

Re: Composite Datums containing toasted fields are a bad idea(?) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Composite Datums containing toasted fields are a bad idea(?)
Date
Msg-id 32232.1396042435@sss.pgh.pa.us
Whole thread Raw
In response to Re: Composite Datums containing toasted fields are a bad idea(?)  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Tree view 
Merlin Moncure <mmoncure@gmail.com> writes:
> Trying to follow along here.  Am I correct in saying that if you make
> these changes any SQL level functionality (say, creating a composite
> type containing a large array) that used to work will continue to
> work?

This wouldn't change any SQL-level functionality ... as long as we don't
introduce new bugs :-(
        regards, tom lane

pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Composite Datums containing toasted fields are a bad idea(?)
Next
From: "Erik Rijkers"
Date:
Subject: Re: trgm regex index peculiarity