pgsql: Rename functions to avoid future conflicts

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Rename functions to avoid future conflicts
Date: 2022-01-10 08:41:35
Message-ID: E1n6qFD-0008RG-Iu@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Rename functions to avoid future conflicts

Rename range_serialize/range_deserialize to
brin_range_serialize/brin_range_deserialize, since there are already
public range_serialize/range_deserialize in rangetypes.h.

Author: Paul A. Jungwirth <pj(at)illuminatedcomputing(dot)com>
Discussion: https://www.postgresql.org/message-id/CA+renyX0ipvY6A_jUOHeB1q9mL4bEYfAZ5FBB7G7jUo5bykjrA@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/ee419607381dd9a8031f2bc226c742a3289b7f33

Modified Files
--------------
src/backend/access/brin/brin_minmax_multi.c | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2022-01-10 11:27:53 pgsql: Make EXEC_BACKEND more convenient on Linux and FreeBSD.
Previous Message Tom Lane 2022-01-10 00:19:28 pgsql: Prefer $HOME when looking up the current user's home directory.