Re: RLS Design

From: "Brightwell, Adam" <adam(dot)brightwell(at)crunchydatasolutions(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Yeb Havinga <yeb(dot)havinga(at)portavita(dot)nl>
Subject: Re: RLS Design
Date: 2014-07-17 01:49:50
Message-ID: CAKRt6CSyeq4=YgoSo+nvEKSngk9313-xB4TuqEf2byM4B7tK0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

Thanks for the feedback.

20MB messages to the list aren't that friendly. Please don't do that
> again, unless asked to.
>

Apologies, I didn't realize it was so large until after it was sent. At
any rate, it won't happen again.

> FWIW, the above syntax is a nonstarter, at least unless we're willing to
> make POLICY a reserved word (hint: we're not). The reason is that the
> ADD/DROP COLUMN forms consider COLUMN to be optional, meaning that the
> column name could directly follow ADD; and the column type name, which
> could also be just a plain identifier, would directly follow that. So
> there's no way to resolve the ambiguity with one token of lookahead.
> This actually isn't just bison being stupid: in fact, you simply
> cannot tell whether
>
> ALTER TABLE tab ADD POLICY varchar(42);
>
> is an attempt to add a column named "policy" of type varchar(42), or an
> attempt to add a policy named "varchar" with quals "42".
>

Ok. Make sense and I was afraid that was the case.

Thanks,
Adam

--
Adam Brightwell - adam(dot)brightwell(at)crunchydatasolutions(dot)com
Database Engineer - www.crunchydatasolutions.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Brightwell, Adam 2014-07-17 02:04:27 Re: RLS Design
Previous Message Stephen Frost 2014-07-17 01:35:59 Re: Question about src/timezone/zic.c