On Wed, Feb 15, 2012 at 5:38 AM, Christoph Berg <c...@df7cb.de> wrote: > diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml > index e45c258..ee0a255 100644 > *** a/doc/src/sgml/sepgsql.sgml > --- b/doc/src/sgml/sepgsql.sgml > *************** UPDATE t1 SET x = 2, y = md5sum(y) WHERE > *** 358,364 **** > </synopsis> > > In this case we must have <literal>db_table:select</> in addition to > ! <literal>db_table:update</>, because <literal>t1.a</> is referenced > within the <literal>WHERE</> clause. Column-level permissions will also > be > checked for each referenced column. > </para> > --- 358,364 ---- > </synopsis> > > In this case we must have <literal>db_table:select</> in addition to > ! <literal>db_table:update</>, because <literal>t1.z</> is referenced > within the <literal>WHERE</> clause. Column-level permissions will also > be > checked for each referenced column. > </para>
Fixed, but note that I had to recreate the patch by manual examination. Including it inline tends to garble things. > (It is unclear to me why the same example is cited twice here, but the > text around them is consistent with that.) Fixed this too, and did some related rewording and proofreading. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
