Re: BUG #15344: pg_proc.proisagg was removed incompatibly in PostgreSQL 11

From: Andres Freund <andres(at)anarazel(dot)de>
To: lukas(dot)eder(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15344: pg_proc.proisagg was removed incompatibly in PostgreSQL 11
Date: 2018-08-21 14:28:21
Message-ID: 20180821142821.m7i73ntdz34rs7ww@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2018-08-21 14:23:45 +0000, PG Bug reporting form wrote:
> When comparing the current version (10) [1] and the developer version (11)
> [2] of the pg_proc documentation, then it can be seen that the
> pg_proc.proisagg column was removed backwards incompatibly. The
> documentation states for [1]:

Please note that the pg_catalog.* tables (and views) are *NOT* intended
to backwards compatible between major versions. We change them in ways
backward incompatible all the time.

> While I appreciate that an encoded enumeration is more powerful than a
> simple boolean value, I think it would have been better if this change had
> been done backwards compatibly. For example, there could still be a
> pg_proc.proisagg column that defaults to (prokind = 'a').

When could we have removed that? The few people querying it would've
continued to rely on it until we've removed it, leading to the same
outcry. And supporting both would've required more code, because we
would have to make sure they're consistent, and raise errors etc if not.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Lukas Eder 2018-08-21 14:39:18 Re: BUG #15344: pg_proc.proisagg was removed incompatibly in PostgreSQL 11
Previous Message PG Bug reporting form 2018-08-21 14:23:45 BUG #15344: pg_proc.proisagg was removed incompatibly in PostgreSQL 11