Re: Oops - BF:Mastodon just died - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Oops - BF:Mastodon just died
Date
Msg-id 8648.1201795623@sss.pgh.pa.us
Whole thread Raw
In response to Re: Oops - BF:Mastodon just died  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Oops - BF:Mastodon just died
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> It strikes me that the pattern needs to be {3,} or maybe just +.
>> I dunno what this column is measuring, but if we are past 0xA00
>> then surely 0x1000 is not far away.

> http://msdn2.microsoft.com/en-us/library/b842y285(VS.71).aspx appears to 
> suggest that the size of the field is fixed.

That would imply that dumpbin fails at 4096 symbols per file.  While I
surely wouldn't put it past M$ to have put in such a limitation, I think
it's more likely that the documentation is badly written.

In any case it would be easy enough to make up a quick test to see what
happens with say
void func1() {}void func2() {}...void func5000() {}

        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)
Next
From: Gregory Stark
Date:
Subject: Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable