> >>> I'm also seeing a lot of signed/unsigned mismatch, but 
> IIRC it was 
> >>> said at some point that we don't care about those.
> >> 
> >> In HEAD?  They're all cleaned up according to the compilers I use.
> > Yup.
> > More digging then I guess. Probably a #define that's messe dup 
> > somewhere.
> Maybe the issue is in Windows-specific code?  I have no idea 
> what the warning status is for that stuff.  In all the stuff 
> I regularly compile, there are only a couple of warnings and 
> they are flex's fault (so there's not much we can do about 
> 'em).  I think it's good to get rid of noise warnings as much 
> as possible --- otherwise they can make you miss important ones.

Probably. I'll see what I can find. It could also be my build being
broken (I've hacked up the build system pretty bad right now), but I
think I used to see this before as well. Will get back to you on this


---------------------------(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

Reply via email to