On Mon, May 14, 2012 at 09:21:20AM +0200, Albe Laurenz wrote:
> Noah Misch wrote:
> > Just thinking out loud, we could provide an "extern Datum
> AnalyzeWideValue;"
> > and direct FDW authors to use that particular datum.  It could look
> like a
> > toasted datum of external size WIDTH_THRESHOLD+1 but bear
> va_toastrelid ==
> > InvalidOid.  Then, if future code movement leads us to actually
> examine one of
> > these values, we'll get an early, hard error.
> 
> That would be very convenient indeed.
> 
> Even better would be a function
> extern Datum createAnalyzeWideValue(integer width)
> so that row width calculations could be more accurate.

Yes; good call.

In response to

• Re: Analyzing foreign tables & memory problems at 2012-05-14 07:21:20 from Albe Laurenz

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2012-05-15 14:17:49
	Subject: Re: Why do we still have commit_delay and commit_siblings?
Previous:	From: Martin Pitt	Date: 2012-05-15 12:25:00
	Subject: 9.2beta1 regression: pg_restore --data-only does not set sequence values any more