> > but there was no patch enclosed or following.
> My copy of the message has the patch by here it is again.
Oh! I have that patch. I am gathering from the rest of your message that
there are two patches being discussed, but had expected a patch having
to do with source code fixups in that message. Sorry I am befuddled and
confused...
> Sounds good to me but why not discuss it on hackers?
Sure.
> > ... an interim solution might include using similar
> > techniques on the inet/cidr types.
> That's what my patch that I haven't submitted does.
OK, sorry, I was confused about which patches do what. How about
submitting your inet/cidr NULL fixup patch for both v6.4.1 and the
development tree?
Then I would propose that we renew this discussion on general
improvements in a short while (~ 3 weeks?) to give v6.4 time to settle
in and me/us time to recover. Pretty tapped out from the last month of
Postgres. But scrubbing the NULL mechanisms is on my list of interests
for v6.5, so would like us to have a solid couple of months to work on
it, and it sounds like Jan and others will want to contribute.
- Tom