Re: LOCK TABLE Permissions

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
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 18:55:07
Message-ID: CAB7nPqQvEqnDdMzBdqVZ8J8-VVH76dvcSdaeCMfanM2LprTV-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-05-11 19:01:50 Re: LOCK TABLE Permissions
Previous Message Robbie Harwood 2015-05-11 18:51:27 Re: Postgres GSSAPI Encryption