On 04/28/12 17:17, Jeff Frost wrote:
> Since I had a theory that it's probably stalling on pg_catalog access, one of
> the guys wrote a test harness that makes several connections and creates and
> drops lots of temp tables. That does seem to allow us to reproduce the issue
> in the production D
The following bug has been logged on the website:
Bug reference: 6622
Logged by: ld.so.1: initdb: fatal: libxsit.so.1: open failed: No such
file or directory
Email address: mng5...@gmail.com
PostgreSQL version: 9.1.0
Operating system: Solaris 10
Description:
Dear Sup
>> On the whole though, I think this is an invented problem. We've never
>> heard a complaint from the field about it.
>
> I think process title seems reasonable. We do that for archiver for
> example, to tell you where it's writing, don't we?
Yes, we do.
This isn't an invented problem; a brie
wrote:
> PostgreSQL version: 9.1.0
Please update to 9.1.3.
http://www.postgresql.org/support/versioning/
> Operating system: Solaris 10
> initdb -D /u01/app/postgres/postgres_data
> ld.so.1: initdb: fatal: libxslt.so.1: open failed: No such file or
> directory
> Killed
My first instinc
Josh Berkus writes:
> This isn't an invented problem; a brief canvass on IRC shows that people
> run into issues with log_collector reloads fairly commonly. However,
> it's pretty low priority, certainly -- never rises above the level of
> "annoyance". The sort of thing where it would be good to
