pgsql: Prevent mis-encoding of "trailing junk after numeric literal" er

Prevent mis-encoding of "trailing junk after numeric literal" errors. Since commit 2549f0661, we reject an identifier immediately following a numeric literal (without separating whitespace), because that risks ambiguity with hex/octal/binary integers. However, that patch used token patterns like

pgsql: Prevent mis-encoding of "trailing junk after numeric literal" er

Prevent mis-encoding of "trailing junk after numeric literal" errors. Since commit 2549f0661, we reject an identifier immediately following a numeric literal (without separating whitespace), because that risks ambiguity with hex/octal/binary integers. However, that patch used token patterns like

pgsql: Prevent mis-encoding of "trailing junk after numeric literal" er

Prevent mis-encoding of "trailing junk after numeric literal" errors. Since commit 2549f0661, we reject an identifier immediately following a numeric literal (without separating whitespace), because that risks ambiguity with hex/octal/binary integers. However, that patch used token patterns like

pgsql: Prevent mis-encoding of "trailing junk after numeric literal" er

Prevent mis-encoding of "trailing junk after numeric literal" errors. Since commit 2549f0661, we reject an identifier immediately following a numeric literal (without separating whitespace), because that risks ambiguity with hex/octal/binary integers. However, that patch used token patterns like