From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: OCLASS_FOREIGN_TABLE support is incomplete |
Date: | 2011-02-05 18:05:01 |
Message-ID: | AANLkTik4HrDLnJVQFGGz=e314W+tfF2dEMz5xy1adfLY@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Feb 5, 2011 at 10:56 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Err... wait. Actually, I think the right thing to do might be to
>> remove OCLASS_FOREIGN_TABLE altogether. I don't think it's actually
>> used for anything. For a foreign table, we use OCLASS_CLASS, just as
>> we do for indexes and sequences. I think that's just leftover crap
>> that I failed to rip out.
>
> OK. I'll fix it as part of the extensions patch, since it's touching
> all those same places anyway.
Excellent, thanks!
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-02-05 18:10:12 | Re: is_absolute_path incorrect on Windows |
Previous Message | Kevin Grittner | 2011-02-05 17:58:13 | Re: SSI patch version 14 |