Peter Eisentraut <[EMAIL PROTECTED]> writes: > Has anyone thought of what will happen to the server_encoding parameter > when the character set/encoding will be settable for individual columns > and the concept of a global server encoding will go away? What will > happen to clients that make use of this parameter?
I would imagine that we'd keep the concept of a per-database encoding, but it would be become a default value for per-column encoding choices, rather than the One True Value. Clients could probably still make use of server_encoding, though I'm unclear on what they'd use it for now, let alone then. ISTM client_encoding is the only setting the client need deal with directly. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org