| From: | Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Eric Davies <eric(at)barrodale(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQL/MED estimated time of arrival? |
| Date: | 2010-11-23 12:22:17 |
| Message-ID: | 20101123212216.96DE.6989961C@metrosystems.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 23 Nov 2010 12:30:52 +0200
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> The docs need some work. The CREATE FOREIGN TABLE reference page seems
> to be copy-pasted from CREATE TABLE, because it talks about constraints
> and WITH/WITHOUT OIDS which surely don't apply to foreign tables.
Thanks for the comments.
The page you pointed has been edited for foreign table. In current
design, OID system column and CHECK constraints are supported.
OID is supported to get oid from the source table (yes, it works only
for postgresql_fdw but it seems useful to support). CHECK constraint
is supported to enable constraint exclusion. In addition, TABLEOID is
supported to show which table is the actual source.
I agree that some kind of documents, such as "How to create new FDW",
should be written.
Regards,
--
Shigeru Hanada
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-11-23 14:02:01 | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |
| Previous Message | Heikki Linnakangas | 2010-11-23 10:38:50 | Re: Extensions, this time with a patch |