Re: Let psql process files with > 4,294,967,295 lines - Mailing list pgsql-hackers

From David Fetter
Subject Re: Let psql process files with > 4,294,967,295 lines
Date
Msg-id 20060731023751.GY2654@fetter.org
Whole thread Raw
In response to Re: Let psql process files with > 4,294,967,295 lines  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Let psql process files with > 4,294,967,295 lines
Re: Let psql process files with > 4,294,967,295 lines
Re: Let psql process files with > 4,294,967,295 lines
List pgsql-hackers
On Sun, Jul 30, 2006 at 05:40:16PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > David Fetter wrote:
> >> This patch changes the data type from unsigned int to unsigned
> >> long long, which is probably not the correct thing in order to
> >> get 64-bit arithmetic, but I figure it's good enough to get a
> >> discussion started.
>
> > The only thing I can tell you is that you should use INT64_FORMAT
> > instead of %lld.
>
> And the datatype should be declared int64, not "long long" which
> doesn't exist everywhere.
>
> Actually you probably want uint64 and UINT64_FORMAT...
>
>             regards, tom lane

I think this fixes it, but I'm unsure how to test it.  Two of the
methods mentioned in IRC, attaching with gdb and setting to a value >
2^32, and setting it directly in some code, seem like OK approaches.

Cheers,
D
--
David Fetter <david@fetter.org> http://fetter.org/
phone: +1 415 235 3778        AIM: dfetter666
                              Skype: davidfetter

Remember to vote!

Attachment

pgsql-hackers by date:

Previous
From: Kenneth Marshall
Date:
Subject: Re: Hash indexes (was: On-disk bitmap index patch)
Next
From: Tom Lane
Date:
Subject: Re: Let psql process files with > 4,294,967,295 lines