Skip site navigation (1) Skip section navigation (2)

Re: 64-bit pgbench V2

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 64-bit pgbench V2
Date: 2010-07-06 00:32:17
Message-ID: AANLkTill9PpjmUxiHx7hScosM7E2zB6f4h2Z1lnQrpRd@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Jul 5, 2010 at 8:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Greg Smith <greg(at)2ndquadrant(dot)com> writes:
>> The main tricky part was figuring how to convert the \setshell
>> implementation.  That uses strtol to parse the number that should have
>> been returned by the shell call.  It turns out there are a stack of ways
>> to do something similar but return 64 bits instead:
>
> Please choose a way that doesn't introduce new portability assumptions.
> The backend gets along fine without strtoll, and I don't see why pgbench
> should have to require it.

It doesn't seem very palatable to have multiple handwritten integer
parsers floating around the code base either.  Maybe we should try to
standardize something and ship it in src/port, or somesuch.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-07-06 00:38:57
Subject: Re: logistics for beta3
Previous:From: Tom LaneDate: 2010-07-06 00:17:24
Subject: Re: 64-bit pgbench V2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group