Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Let psql process files with > 4,294,967,295 lines
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- Cc: David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Let psql process files with > 4,294,967,295 lines
- Date: Sun, 30 Jul 2006 17:40:16 -0400
Alvaro Herrera <alvherre(at)commandprompt(dot)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
- Follow-Ups:
- Re: Let psql process files with > 4,294,967,295 lines
- From: David Fetter
- Re: Let psql process files with > 4,294,967,295 lines
- References:
- Let psql process files with > 4,294,967,295 lines
- From: David Fetter
- Re: Let psql process files with > 4,294,967,295 lines
- From: Alvaro Herrera
- Let psql process files with > 4,294,967,295 lines
- Prev by Date: Re: Let psql process files with > 4,294,967,295 lines
- Next by Date: Re: request: support of array in plperl OUT arguments
- Previous by thread: Re: Let psql process files with > 4,294,967,295 lines
- Next by thread: Re: Let psql process files with > 4,294,967,295 lines
- Indexes: