From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Andrew Dunstan <andrew(at)dunslane(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 14:45:07 |
Message-ID: | 6450.1201790707@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-01-31 14:47:26 | Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable) |
Previous Message | Simon Riggs | 2008-01-31 14:33:53 | Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable |