Re: sepgsql: fix relkind handling on foreign tables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Cc: PgHacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: sepgsql: fix relkind handling on foreign tables
Date: 2011-05-23 18:26:15
Message-ID: BANLkTin4uWgvQGf+gbfM8P3wEbGy4r_Xhg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, May 22, 2011 at 5:52 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> The attached patch fixes up case handling in foreign tables.
>
> Now it didn't assign security label on foreign table on its creation
> time, and didn't check access rights on the dml hook.
> This patch fixes these problems; It allows foreign tables default
> labeling and access checks as db_table object class.

A foreign table is really more like a view, or a function call. Are
you sure you want to handle it like a table?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dan Ports 2011-05-23 18:32:33 Re: SSI predicate locking on heap -- tuple or row?
Previous Message Robert Haas 2011-05-23 18:11:39 Re: Identifying no-op length coercions