| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>, Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>, Jan Urbański <wulczer(at)wulczer(dot)org> |
| Subject: | Re: review: FDW API |
| Date: | 2011-02-15 20:37:36 |
| Message-ID: | 4D5AE410.80301@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15.02.2011 21:00, Robert Haas wrote:
> On Tue, Feb 15, 2011 at 1:40 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> I'm actually surprised we don't need to distinguish them in more places, but
>> nevertheless it feels like we should have that info available more
>> conveniently, and without requiring a catalog lookup like get_rel_relkind()
>> does. At first I thought we should add a field to RelOptInfo, but that
>> doesn't help transformLockingClause. Adding the field to RangeTblEntry seems
>> quite invasive, and it doesn't feel like the right place to cache that kind
>> of information anyway. Thoughts on that?
>
> Maybe it should be a new RTEKind.
That would be even more invasive.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-15 21:00:03 | Re: review: FDW API |
| Previous Message | Heikki Linnakangas | 2011-02-15 20:36:58 | Re: review: FDW API |