Re: CATUPDATE confusion?

From: Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CATUPDATE confusion?
Date: 2015-03-06 15:36:25
Message-ID: CAKRt6CQUA+mFS0Qcoe862R1hyeae+ZOHK=C1Eza9RgtCFYSEUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

All,

Thanks for all the feedback and review.

> I think I vote for (1). I do not like (2) because of the argument I made
> > upthread that write access on system catalogs is far more dangerous than
> > a naive DBA might think. (0) has some attraction but really CATUPDATE
> > is one more concept than we need.
>
> I agree with #1 on this.
>

#1 makes sense to me as well. The current version of the patch takes this
approach. Also, I have verified against 'master' as of c6ee39b.

Thanks,
Adam

--
Adam Brightwell - adam(dot)brightwell(at)crunchydatasolutions(dot)com
Database Engineer - www.crunchydatasolutions.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-03-06 15:49:02 Re: MD5 authentication needs help
Previous Message Stephen Frost 2015-03-06 15:30:08 Re: MD5 authentication needs help