| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Analyzing foreign tables & memory problems |
| Date: | 2012-05-15 13:08:08 |
| Message-ID: | 20120515130808.GC25848@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-05-15 14:17:49 | Re: Why do we still have commit_delay and commit_siblings? |
| Previous Message | Martin Pitt | 2012-05-15 12:25:00 | 9.2beta1 regression: pg_restore --data-only does not set sequence values any more |