Re: CATUPDATE confusion?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CATUPDATE confusion?
Date: 2014-12-27 23:26:02
Message-ID: 1952.1419722762@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> Plan C (remove CATUPDATE altogether) also has some merit. But adding a
>> superuser override there would be entirely pointless.

> This is be my recommendation. I do not see the point of carrying the
> option around just to confuse new users of pg_authid and reviewers of
> the code.

Yeah ... if no one's found it interesting in the 20 years since the
code left Berkeley, it's unlikely that interest will emerge in the
future.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2014-12-27 23:31:50 Re: CATUPDATE confusion?
Previous Message Stephen Frost 2014-12-27 23:18:29 Re: CATUPDATE confusion?