Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> Dave Page wrote:
>>> Any eta on a fix for this? My internal builds are failing as well as
>>> red_bat. (and yes, the other 2 MSVC buildfarm members are currently
>>> waiting for Dell to get hold of a new motherboard for their box).
>> I think the maintenance of the MSVC build system is the job of the,
>> well, maintainer of the MSVC build system, whoever that may be. In
>> other words, I have no ETA for you from me. I'd be glad, however, to
>> provide information to the maintainers.
> I do not think this is an appropriate attitude for a committer to take.
> You are responsible for what you commit. If you don't have the
> knowledge to fix something, or the resources to test it, okay ... but
> you then need to be proactive about getting someone else to fix/test it.
> Or else revert the broken patch.
I agree. I have committed an attempted fix which I discussed briefly
In response to
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2008-12-16 15:57:56|
|Subject: Re: SQL/MED compatible connection manager|
|Previous:||From: Tom Lane||Date: 2008-12-16 14:56:24|
|Subject: Re: [BUG?] UPDATE with RETURNING tableoid |
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2008-12-16 16:26:08|
|Subject: pgsql: Make heap_update() set newtup->t_tableOid correctly, for |
|Previous:||From: Andrew Dunstan||Date: 2008-12-16 15:42:21|
|Subject: pgsql: Attempt to fix MSVC breakage from Major Version patch.|