Hi,
I'm dutifully reporting some warnings I received when initializing a
postgresql database.
The command I ran was this:
sudo -u postgres /opt/local/lib/postgresql84/bin/initdb -E UTF-8 -D
/opt/local/var/db/postgresql84/defaultdb
(I had tried before without the '-E UTF-8' option, but that
Wes Sheldahl wes.sheld...@gmail.com writes:
copying template1 to template0 ... WARNING: could not determine
encoding for locale en_US.US-ASCII: codeset is US-ASCII
DETAIL: Please report this to pgsql-bugs@postgresql.org.
Thanks for the report. We have already modified CVS HEAD to default
to
That's better, I was worried you'd gone all complimentary on me.
grinNever fear that!
Was that setting originally part of your design for HS? If so, why did
you back off from it?
--Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
On Sat, 2010-03-13 at 11:29 -0800, Josh Berkus wrote:
That's better, I was worried you'd gone all complimentary on me.
grinNever fear that!
Was that setting originally part of your design for HS? If so, why did
you back off from it?
We all agreed its a kluge, that's why.
It's also my
On Thu, Mar 4, 2010 at 5:55 AM, ALEX bav...@mail.ru wrote:
The following bug has been logged online:
Bug reference: 5362
Logged by: ALEX
Email address: bav...@mail.ru
PostgreSQL version: 8.3
Operating system: linux ubuntu 9.10 server
Description: WARNING could
Robert Haas robertmh...@gmail.com writes:
On Thu, Mar 4, 2010 at 5:55 AM, ALEX bav...@mail.ru wrote:
could not determine encoding for locale uk_UA.koi8u: codeset is KOI8-U
Do we need to do anything about this?
Should be fixed in 8.4 and up.
regards, tom lane
--
Sent
It's also my 3rd choice of solution behind fine-grained lock conflicts
(1st) which would avoid many issues and master/standby in lock step
(2nd).
Yeah, I just can't imagine you hunting down all of the corner cases for
fine-grained lock conflicts in time for 9.0. Given what I've been
looking
