pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Corey Huinker <corey.huinker@gmail.com>
Cc: Daniel Verite <daniel@manitou-mail.org>
Cc: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: Variable substitution in psql backtick expansion
Date: Mon, 04 Sep 2017 12:56:28 -0400
Message-ID: <4172.1504544188@sss.pgh.pa.us> (raw )
In-Reply-To: <2947.1504542679@sss.pgh.pa.us >
References: <bc15034d-b421-42ac-89b1-c3485fa1728b@manitou-mail.org >
<CAFj8pRACH1M=egydH4dAAoo9rRVTkuYCaoyZQK2Yf4BTQuRM5w@mail.gmail.com >
<CADkLM=dzsbgJdP7KAJnbihxU1XFnWZgit9ye5cWnvkjZXyPbGw@mail.gmail.com >
<alpine.DEB.2.20.1704021805550.4632@lancre >
<CADkLM=c+hm2rc0tkKgC-ZgrLttHT2KkfppE+BC-=i-xj+7V-TQ@mail.gmail.com >
<3926.1491159242@sss.pgh.pa.us >
<alpine.DEB.2.20.1704022151080.9265@lancre >
<CAFj8pRDyaC+FaSxd92CLcuV+UFGhwY7NVVBhqFvxPkhvKNhyww@mail.gmail.com >
<alpine.DEB.2.20.1705211737030.6053@lancre >
<CA+TgmobT3rD6jaZMCs=PWH_khMu6Bb4TwX+r4tbTNA41hx32=w@mail.gmail.com >
<13303.1503698976@sss.pgh.pa.us >
<CA+TgmobXCcEM7uB8_g+tKfB-1gvEyp+Qmmre9bcXU9mgpmW38Q@mail.gmail.com >
<14596.1503701034@sss.pgh.pa.us >
<alpine.DEB.2.20.1708260747110.3627@lancre >
<20786.1503760136@sss.pgh.pa.us >
<alpine.DEB.2.20.1708261740590.17521@lancre >
<24850.1503766425@sss.pgh.pa.us >
<alpine.DEB.2.20.1708261959560.27500@lancre >
<4959.1503774468@sss.pgh.pa.us >
<alpine.DEB.2.20.1708270811060.18068@lancre >
<2947.1504542679@sss.pgh.pa.us >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
I wrote:
> ... Or maybe we should shorten this
> variable name so it doesn't force reformatting of all this text.
> Possible ideas include "DB_VERSION_NAME", "SERVER_VER_NAME", or
> "SERVER_VERSION_STR". (The last saves only one character, whereas
> we really need to save two if we're trying not to be wider than any
> other documented variable.)
Just had another idea: maybe make the new variable names
SERVER_VERSION_S
SERVER_VERSION_N
VERSION_S
VERSION_N
"_S" could usefully be read as either "string" or "short", and probably
we should document it as meaning "short". This way avoids creating any
weird inconsistencies with the existing precedent of the VERSION variable.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (96+ messages) latest in thread
Message-ID: <4172.1504544188@sss.pgh.pa.us>
Permalink: ../4172.1504544188@sss.pgh.pa.us/
Also on: postgresql.org/message-id/4172.1504544188@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, coelho@cri.ensmp.fr, robertmhaas@gmail.com, pavel.stehule@gmail.com, corey.huinker@gmail.com, daniel@manitou-mail.org
Subject: Re: Variable substitution in psql backtick expansion
In-Reply-To: <4172.1504544188@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox