| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQL/MED - file_fdw |
| Date: | 2011-02-21 16:36:52 |
| Message-ID: | 15159.1298306212@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thom Brown <thom(at)linux(dot)com> writes:
> Is this right?
> postgres=# \d+ agg_text
> Foreign table "public.agg_text"
> Column | Type | Modifiers | Storage | Description
> --------+----------+-----------+----------+-------------
> a | smallint | | plain |
> b | text | | extended |
> Server: file_server
> Has OIDs: no
> It says the agg_text foreign table is using extended storage for the
> text field. If it's in-file, how can it be classified as potentially
> TOASTed?
It's meaningless, but I don't think it's worth trying to suppress the
meaningless column(s) ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-02-21 16:38:14 | Re: FDW API: don't like the EXPLAIN mechanism |
| Previous Message | Tom Lane | 2011-02-21 16:23:36 | Re: FDW API: don't like the EXPLAIN mechanism |