Re: pgsql: Fix unportable code in pgbench.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Fix unportable code in pgbench.
Date: 2019-04-17 21:57:14
Message-ID: 30311.1555538234@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>> Fix unportable code in pgbench.

> Sorry for this unforseen issue... portability is a pain:-(

I think it's my fault, actually --- I don't remember how much of
that patch was yours.

> Yep, but ISTM that it is down to 32 bits,

Only on 32-bit-long machines, which are a dwindling minority (except
for Windows, which I don't really care about).

> So the third short is now always 0. Hmmm. I'll propose another option over
> the week-end.

I suppose we could put pg_strtouint64 somewhere where pgbench can use it,
but TBH I don't think it's worth the trouble. The set of people using
the --random-seed=int option at all is darn near empty, I suspect,
and the documentation only says you can write an int there.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2019-04-17 22:01:17 pgsql: docs: clarify pg_upgrade's recovery behavior
Previous Message Fabien COELHO 2019-04-17 21:46:09 Re: pgsql: Fix unportable code in pgbench.

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-04-17 22:06:00 Re: pg_dump is broken for partition tablespaces
Previous Message Tom Lane 2019-04-17 21:51:21 Re: pg_dump is broken for partition tablespaces