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

From Tom Lane
Subject Re: Oops - BF:Mastodon just died
Date
Msg-id 6450.1201790707@sss.pgh.pa.us
Whole thread Raw
In response to Re: Oops - BF:Mastodon just died  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Oops - BF:Mastodon just died  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
>> Andrew Dunstan <andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
Next
From: Alvaro Herrera
Date:
Subject: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)