Gregory Stark <[EMAIL PROTECTED]> writes:
> ... This puts the order back in sync. I don't haven't looked at the
> surrounding code enough to know if there aren't more problems like this
> lurking or if there's a way to fix it so it isn't such a pain to maintain.

The real problem is I believed the comment in pg_wchar.h that told me
the only table that needed fixed was pg_enc2name :-(

A check of Tatsuo's last couple of encoding-related commits confirms
that there are only two order-sensitive tables, though, so I think
we're good now.  Also this time I troubled to run the src/test/mb/
tests, which I really should have tried earlier.  Ah well.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to