Re: pgsql: pg_collation_actual_version() -> pg_collation_current_version().

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: pg_collation_actual_version() -> pg_collation_current_version().
Date: 2021-02-23 06:03:12
Message-ID: 2e30284c-1440-a98a-43fe-ad6ebc7a10bb@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 22.02.21 12:28, Thomas Munro wrote:
> pg_collation_actual_version() -> pg_collation_current_version().
>
> The new name seems a bit more natural.
>
> Discussion: https://postgr.es/m/20210117215940.GE8560%40telsasoft.com

I don't find where this change was discussed in that thread. I
specifically chose that name to indicate, "not the current version in
the database, but the version the OS thinks it should be". I think the
rename loses that distinction.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2021-02-23 07:23:19 Re: pgsql: pg_collation_actual_version() -> pg_collation_current_version().
Previous Message Amit Kapila 2021-02-23 04:28:36 pgsql: Fix an oversight in ReorderBufferFinishPrepared.

Browse pgsql-hackers by date

  From Date Subject
Next Message houzj.fnst@fujitsu.com 2021-02-23 06:12:28 RE: A reloption for partitioned tables - parallel_workers
Previous Message Tom Lane 2021-02-23 05:50:41 Re: pg_temp_%d namespace creation can invalidate all the cached plan in other backends