>In existing releases, the SQL definitions are set_bit(bytea,int4,int4) >and get_bit(bytea,int4) and cannot be changed to not break the API. >So the patch meant for existing releases has to deal with a too-narrow >int32 bit number. >Internally in the C functions, you may convert that number to int64 >if you think it's necessary, but you may not use PG_GETARG_INT64 >to pick a 32-bit argument. The input parameter of 'set_bit()' function for 'byteaGetBit' has changed to 'bytea int8 int4', but maybe another 'set_bit()' for 'bitgetbit' need not changed. The same with 'get_bit()'.
Regards, Highgo Software (Canada/China/Pakistan) URL : www.highgo.ca EMAIL: mailto:movead(dot)li(at)highgo(dot)ca
