pgsql: Doc: fix oversimplified example for CREATE POLICY.

2018-07-30 Thread Tom Lane
Doc: fix oversimplified example for CREATE POLICY. As written, this policy constrained only the post-image not the pre-image of rows, meaning that users could delete other users' rows or take ownership of such rows, contrary to what the docs claimed would happen. We need two separate policies to a

pgsql: Doc: fix oversimplified example for CREATE POLICY.

2018-07-30 Thread Tom Lane
Doc: fix oversimplified example for CREATE POLICY. As written, this policy constrained only the post-image not the pre-image of rows, meaning that users could delete other users' rows or take ownership of such rows, contrary to what the docs claimed would happen. We need two separate policies to a

pgsql: Doc: fix oversimplified example for CREATE POLICY.

2018-07-30 Thread Tom Lane
Doc: fix oversimplified example for CREATE POLICY. As written, this policy constrained only the post-image not the pre-image of rows, meaning that users could delete other users' rows or take ownership of such rows, contrary to what the docs claimed would happen. We need two separate policies to a

pgsql: Doc: fix oversimplified example for CREATE POLICY.

2018-07-30 Thread Tom Lane
Doc: fix oversimplified example for CREATE POLICY. As written, this policy constrained only the post-image not the pre-image of rows, meaning that users could delete other users' rows or take ownership of such rows, contrary to what the docs claimed would happen. We need two separate policies to a

pgsql: Doc: fix oversimplified example for CREATE POLICY.

2018-07-30 Thread Tom Lane
Doc: fix oversimplified example for CREATE POLICY. As written, this policy constrained only the post-image not the pre-image of rows, meaning that users could delete other users' rows or take ownership of such rows, contrary to what the docs claimed would happen. We need two separate policies to a