On Wed, 2020-05-27 at 14:42 -0700, Michel Pelletier wrote:
> Hi Marc,
>
> You can sign content with pgsodium:
>
> https://github.com/michelp/pgsodium
Michel,
Yay! A modern crypto implementation. And it seems to do most of what
I need right out of the box with way less work than pgcrypto.
Any
On Tue, 2020-05-26 at 12:04 -0700, Adrian Klaver wrote:
> On 5/26/20 12:01 PM, Marc Munro wrote:
> > I need to be able to cryptographically sign objects in my database
> > using a public key scheme.
> > [ . . . ]
> > Any other options? Am I missing something?
>
>
I need to be able to cryptographically sign objects in my database
using a public key scheme.
Is my only option to install plpython or some such thing? Python
generally makes me unhappy as I'm never convinced of its stability or
the quality of its APIs, and it is not obvious to me which of the m
On Tue, 2020-02-18 at 15:06 -0500, Stephen Frost wrote:
>
> Policies, also being part of the overall privilege system, could
> certainly be looked at in a similar light as being different from
> triggers and indexes...
While I think I agree with Stephen here, I don't have a vested interest
in an
On Mon, 2020-02-17 at 22:48 -0500, Tom Lane wrote:
> Marc Munro writes:
> >
> An RLS policy is a table "subsidiary object" so it only depends
> indirectly
> on the extension that owns the table.
Yep, I get that, and I see the dependency chain in the catalog.
How
I tried to define a policy within an extension but the policy does not
seem to belong to the extension. Is this the way it is supposed to be?
This is postgres 9.5.21
Here is the relevant code from the extension:
create table rls2 (
username text not null,
details text not null