On 2019-12-10 17:23, Tom Lane wrote:
Peter Eisentraut writes:
Good point. Done in the attached patch.
(If someone wanted to revive the original functionality, it would
nowadays probably be easier to add a flag ATT_SYSTEM_TABLE to
ATSimplePermissions(), so there is really no reason to keep the
Peter Eisentraut writes:
> Good point. Done in the attached patch.
> (If someone wanted to revive the original functionality, it would
> nowadays probably be easier to add a flag ATT_SYSTEM_TABLE to
> ATSimplePermissions(), so there is really no reason to keep the old
> function separate.)
Ye
On 2019-12-05 00:16, Tom Lane wrote:
Seems reasonable. The argument for making this an exception to
allow_system_table_mods was always more about expediency than logical
cleanliness. After the recent changes I think it's okay to remove the
special case (especially since nobody has griped about
Peter Eisentraut writes:
> Until PostgreSQL 9.1, it was possible to run ALTER TABLE ... SET
> STATISTICS without allow_system_table_mods. In PostgreSQL 9.2 and
> later, this no longer works. This change was apparently accidental. (I
> gave up after a while trying to bisect it exactly, but pr
Until PostgreSQL 9.1, it was possible to run ALTER TABLE ... SET
STATISTICS without allow_system_table_mods. In PostgreSQL 9.2 and
later, this no longer works. This change was apparently accidental. (I
gave up after a while trying to bisect it exactly, but probably
something related to 1489e
