Re: postmaster became multithreaded during startup - Mailing list pgsql-bugs

From Noah Misch
Subject Re: postmaster became multithreaded during startup
Date
Msg-id 20160319062259.GA1225981@tornado.leadboat.com
Whole thread Raw
In response to postmaster became multithreaded during startup  (Philip White <philip@mailworks.org>)
Responses Re: postmaster became multithreaded during startup
List pgsql-bugs
On Wed, Mar 16, 2016 at 01:53:57PM -0700, Philip White wrote:
> FATAL:  postmaster became multithreaded during startup
> HINT:  Set the LC_ALL environment variable to a valid locale.

> $ locale
> LANG="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_CTYPE="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_ALL="en_US.UTF-8"
>
> Now that my LC_* variables are correct, I am stumped. Any ideas?

What is the output of "env | grep -E '^(LC|LANG)'"?  "locale" command output
tells us the effective setting for each locale category, but it doesn't tell
us which environment variables or other sources provided those settings.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #14027: n_tup_ins increments regardless of insertion success
Next
From: David Gould
Date:
Subject: Re: BUG #13750: Autovacuum slows down with large numbers of tables. More workers makes it slower.