From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)postgresql(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Oops - BF:Mastodon just died |
Date: | 2008-01-31 15:28:18 |
Message-ID: | 47A1E912.40408@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>
>>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>>
>>>> For now I'm going try to fix it by changing it to:
>>>> next unless $pieces[0] =~/^[A-F0-9]{3}$/;
>>>>
>
>
>> Yeah, nice catch. Wouldn't surprise me if we actually had this problem
>> before, just that the dropped symbols were not actually used by our own
>> modules. I notice the export count jumped to 5226...
>>
>
> I was wondering where the count would go.
>
> 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.
But who knows?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-31 15:28:59 | Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) |
Previous Message | Tom Lane | 2008-01-31 15:25:54 | Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable |