Alex Pilosov <[EMAIL PROTECTED]> writes:
> Just to clarify for stupid me: you want to remove it and forbid catalog
> updates or remove it and allow catalog updates? (I hope its latter :)
Right, the latter. If anyone is actually using usecatupd to prevent
themselves from shooting themselves in th
Just to clarify for stupid me: you want to remove it and forbid catalog
updates or remove it and allow catalog updates? (I hope its latter :)
On Tue, 23 Jan 2001, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > While I'm at it and before I forget the 76 places one needs to edi
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> While I'm at it and before I forget the 76 places one needs to edit to
> add/remove a system catalog column, what are people's feelings about the
> usecatupd column?
Unless someone pops up and says that they're actually using it,
I'd agree with remov
Yes, I vote for removal.
> While I'm at it and before I forget the 76 places one needs to edit to
> add/remove a system catalog column, what are people's feelings about the
> usecatupd column?
>
> The use of this field is that, if false, it disallows any direct
> modification of system catalogs
While I'm at it and before I forget the 76 places one needs to edit to
add/remove a system catalog column, what are people's feelings about the
usecatupd column?
The use of this field is that, if false, it disallows any direct
modification of system catalogs, even for superusers. In the past the
