On Fri, Jan 1, 2010 at 20:33, Tom Lane <t...@sss.pgh.pa.us> wrote: > Magnus Hagander <mag...@hagander.net> writes: >> On Fri, Jan 1, 2010 at 20:12, Peter Eisentraut <pete...@gmx.net> wrote: >>> This shouldn't be a problem for the same reason that casting size_t to >>> int is not a problem in the PostgreSQL backend code, but perhaps writing >>> 1L << ... would fix it. > >> 1L didn't fix it. 1LL did, however. > > ... and would break things on many many other platforms.
That's what I was afraid of. > Use "(Size) 1" instead of "1" if you really want to suppress this. That fixes it as well. Will apply a patch to that effect. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
