Re: public schema default ACL

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: public schema default ACL
Date: 2021-03-27 10:41:07
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Sat, 2021-03-27 at 00:50 -0700, Noah Misch wrote:
> On Sat, Feb 13, 2021 at 04:56:29AM -0800, Noah Misch wrote:
> > I'm attaching the patch for $SUBJECT, which applies atop the four patches from
> > the two other threads below. For convenience of testing, I've included a
> > rollup patch, equivalent to applying all five patches.
> I committed prerequisites from one thread, so here's a rebased rollup patch.

I am happy to see this problem tackled!

Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Lætitia Avrot 2021-03-27 12:22:43 Re: pg_dump new feature: exporting functions only. Bad or good idea ?
Previous Message Floris Van Nee 2021-03-27 10:24:00 RE: non-HOT update not looking at FSM for large tuple update