Stephen Frost <sfr...@snowman.net> writes:
> * Jonathan S. Katz (jk...@postgresql.org) wrote:
>> By that logic, I would +1 removing ENCRYPTED & UNENCRYPTED, given
>> ENCRYPTED effectively has no meaning either after all this time too.
>> Perhaps a stepping stone is to emit a deprecation warning on PG14 and
>> remove in PG15, but I think it's safe to remove.
> We're terrible about that, and people reasonably complain about such
> things because we don't *know* we're gonna remove it in 15.
If we're changing associated defaults, there's already some risk of
breaking badly-written applications. +1 for just removing these
keywords in v14.
regards, tom lane
