On Jan 21, 2010, at 8:54 AM, Greg Sabino Mullane wrote: > Ah, yes, that's unfortunately true - it's too early for the code > to have already parsed and internalized the attribute hash > inside the connect call. It's possible we could set enable_utf8 > to an indeterminate state and default to UTF-8 if we are in that > state. I'm grumpily tempted to just flip it on for all cases :) > but we should probably just clean up all of the UTF-8 stuff at > once be removing the main function of pg_enable_utf8 (while > keeping it for backwards compat, as mentioned in another thread).
+1 David
