| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marti Raudsepp <marti(at)juffo(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Cleanup: unify checks for catalog modification |
| Date: | 2014-10-14 23:10:35 |
| Message-ID: | 28734.1413328235@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marti Raudsepp <marti(at)juffo(dot)org> writes:
> I happened to notice that there are no less than 14 places in the code
> that check whether a relation is a system catalog and throwing the
> error "permission denied: "foo" is a system catalog"
> The attached patch factors all of those into a single
> ForbidSystemTableMods() function. Is this considered an improvement?
I'd argue not. The code bulk savings is minimal, and this change
would degrade the usefulness of the file/line number reporting that's
built into ereport(). Admittedly it's a judgment call --- we've certainly
built error-reporting subroutines in cases where a significant amount of
complexity could be folded into the subroutine. But I don't think this
case meets the threshold.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-10-15 02:00:09 | Re: [PATCH] Cleanup: unify checks for catalog modification |
| Previous Message | Tom Lane | 2014-10-14 23:07:17 | Re: narwhal and PGDLLIMPORT |