From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
cc: Anastasia Lubennikova <a.lubennikova@postgrespro.ru>,
        PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>,
        David Rowley <dgrowleyml@gmail.com>,
        Jaime Soler <jaime.soler@gmail.com>
Subject: Re: pgbench and timestamps (bounced)
In-reply-to: <alpine.DEB.2.22.394.2101131649420.699567@pseudo>
References: <alpine.DEB.2.22.394.2006291740420.805678@pseudo>
 <1720048.1599525071@sss.pgh.pa.us>
 <alpine.DEB.2.22.394.2009111501410.3995562@pseudo>
 <6c6af173-85b9-f0b3-4764-b0df415d2736@postgrespro.ru>
 <alpine.DEB.2.22.394.2011262358470.3117595@pseudo>
 <1236015.1610491076@sss.pgh.pa.us>
 <alpine.DEB.2.22.394.2101131649420.699567@pseudo>
Comments: In-reply-to Fabien COELHO <coelho@cri.ensmp.fr>
	message dated "Wed, 13 Jan 2021 16:53:09 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1304502.1610567719.1@sss.pgh.pa.us>
Date: Wed, 13 Jan 2021 14:55:19 -0500
Message-ID: <1304503.1610567719@sss.pgh.pa.us>
Precedence: bulk

Fabien COELHO <coelho@cri.ensmp.fr> writes:
>> What remains that we could do now, and perhaps back-patch, is point (2)
>> i.e. disallow digits as the first character of a pgbench variable name.

> I'm fine with that.

>> That would be enough to "solve" the original bug report, and it does seem
>> like it could be back-patched, while we're certainly not going to risk
>> back-patching anything as portability-fraught as introducing mutexes.

> Sure.

OK.  I've pushed a patch that just does that much, and marked the
commitfest entry closed.  After the other thing lands, please rebase
and resubmit what remains of this patch.

			regards, tom lane