Re: [HACKERS] Open the flood gates...v6.4 is tag'd...
От | Thomas G. Lockhart |
---|---|
Тема | Re: [HACKERS] Open the flood gates...v6.4 is tag'd... |
Дата | |
Msg-id | 364143CA.373AA9E@alumni.caltech.edu обсуждение исходный текст |
Ответ на | Re: [HACKERS] Open the flood gates...v6.4 is tag'd... (darcy@druid.net) |
Ответы |
Re: [HACKERS] Open the flood gates...v6.4 is tag'd...
|
Список | pgsql-hackers |
> So do I send in my patch or have we decided to fix the null arg > problem in the function dispatcher? I deleted one or a few messages from this thread, but at least one message which I still have (kept them once I realized this issue was blowing up) mentions: >> OK, there are more problems. If you apply the following patch to >> the regression tests you will crash the backend in a number of >> places. but there was no patch enclosed or following. Anyway, I would suggest that, until we plan out what new behaviors we really want in the system that we don't submit a patch which breaks many of the data types. That kind of change should, imho, be done offline and committed as an integrated solution. If you'd like, I'd be happy to trade patches with you as we work out the issues and once we (and anyone else with an interest) are happy with the new behavior and have regression tests which pass then we should commit to the tree. As you mentioned, the date and time functions check for null inputs and behave pretty well, and an interim solution might include using similar techniques on the inet/cidr types. - Tom
В списке pgsql-hackers по дате отправления: