Agent M wrote: > Would the version bump be a good time to fix the "UNICODE" encoding > misnomer in database creation and in the backend param status? I > assume it should be "UTFx".
We could make UTF8 the canonical form in the aliasing mechanism, but beta 4 is a bit late to come up with this kind of idea. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings