On 12.01.23 18:41, Alvaro Herrera wrote:
> I think one important criterion to think about is how does encryption work
> when you have per-customer (or per-whatever) schemas. Is the concept of
> a column encryption [objtype] a thing that you would like to set up per
> customer? In that case, you will probably want that object to live in
> that customer's schema. Otherwise, you'll force the DBA to come up with
> a naming scheme that includes the customer name in the column encryption
> object.
Makes sense. In my latest patch I have moved these key objects into
schemas.
