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

From Bruce Momjian
Subject Re: Let psql process files with > 4,294,967,295 lines
Date
Msg-id 200608111921.k7BJLSd00646@momjian.us
Whole thread Raw
In response to Re: Let psql process files with > 4,294,967,295 lines  (David Fetter <david@fetter.org>)
List pgsql-hackers
Patch applied.  Thanks.  Unnecessary #include file removed.

---------------------------------------------------------------------------



David Fetter wrote:
> 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, skipping... ]

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Coding style for emacs
Next
From: Bruce Momjian
Date:
Subject: Re: Coding style for emacs