Re: LOCK TABLE Permissions

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: LOCK TABLE Permissions
Date: 2015-05-11 19:01:50
Message-ID: 20150511190150.GC30322@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Michael Paquier (michael(dot)paquier(at)gmail(dot)com) wrote:
> On Mon, May 11, 2015 at 10:32 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Now for a blast from the past... This came up again on IRC recently and
> > reminded me that I ran into the same issue a couple years back. Updated
> > patch includes the refactoring suggested and includes documentation.
> >
> > Barring objections, I'll push this later today.
>
> Small suggestion: a test case in src/test/isolation?

This is entirely a permissions-related change and src/test/isolation is
for testing concurrent behavior, not about testing permissions.

I'm not saying that we shouldn't have more tests there, but it'd not
be appropriate for this particular patch.

Thanks!

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhijit Menon-Sen 2015-05-11 19:12:14 Re: a fast bloat measurement tool (was Re: Measuring relation free space)
Previous Message Michael Paquier 2015-05-11 18:55:07 Re: LOCK TABLE Permissions