From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, Jaime Soler <jaime(dot)soler(at)gmail(dot)com> |
Subject: | Re: pgbench and timestamps (bounced) |
Date: | 2021-01-13 19:55:19 |
Message-ID: | 1304503.1610567719@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-01-13 20:26:45 | Re: pg_preadv() and pg_pwritev() |
Previous Message | Thomas Munro | 2021-01-13 19:52:04 | Re: pg_preadv() and pg_pwritev() |