Thomas Lockhart <lockhart@fourpalms.org> writes:
>> But more importantly,
>> at this point in the 7.2 cycle we ought not be making any changes that
>> are not *essential* bug fixes. If you want to reorganize the support
>> for CURRENT_TIMESTAMP() like that, let's leave it for 7.3.
> *grumble* The support for this is already organized. I'm just suggesting
> that we avoid arbitrarily damaging our design and implementation with an
> arbitrary reorganization done in the 7.2 development cycle, and that we
> fix it before it become embedded in a release.
I hear you ... but I think the time to have complained was when Peter
put it in, which was nigh two months ago.
regards, tom lane