Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> I think a reasonable compromise is to turn the ereport() in _dosmaperr
>> to DEBUG1 instead. That way it won't clutter any log by default, and in
>> the cases where we're actually interested in tracking the problematic
>> situation, we don't need to get huge amounts of log traffic coming from
>> other parts of the system.
>
> I'm still not convinced what you think the problematic situation is.
> It's already the case (and reasonable, I think) that _dosmaperr issues a
> LOG message if it sees a GetLastError code it doesn't recognize; that
> addresses the problem that this thread started with. Why do we need to
> make the success case chattier?
I believe Alvaros point is that several different GetLastError codes map
to the same errno code, making it impossible to see the difference
between those errors.
//Magnus
---------------------------(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
match
