| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CATUPDATE confusion? |
| Date: | 2015-03-07 05:31:03 |
| Message-ID: | 4593.1425706263@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On 12/29/14 7:16 PM, Adam Brightwell wrote:
>> Given this discussion, I have attached a patch that removes CATUPDATE
>> for review/discussion.
> committed this version
Hmm .. I'm not sure that summarily removing usecatupd from those three
system views was well thought out. pg_shadow, especially, has no reason
to live at all except for backwards compatibility, and clients might well
expect that column to still be there. I wonder if we'd not be better off
to keep the column in the views but have it read from rolsuper.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2015-03-07 05:33:53 | Re: Question about lazy_space_alloc() / linux over-commit |
| Previous Message | Peter Eisentraut | 2015-03-07 04:43:47 | Re: CATUPDATE confusion? |