Re: Composite Datums containing toasted fields are a bad idea(?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Composite Datums containing toasted fields are a bad idea(?)
Date: 2014-03-28 21:33:55
Message-ID: 32232.1396042435@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Merlin Moncure <mmoncure(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mike Blackwell 2014-03-28 21:36:49 Re: BUG #9518: temporary login failure - "missing pg_hba entry"
Previous Message Merlin Moncure 2014-03-28 21:19:30 Re: Composite Datums containing toasted fields are a bad idea(?)