Re: [BUGS] 9.1.3 backends getting stuck in 'startup'
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 DB, but not in a newly created DB. So, we're about to > initdb a new data directory and slony replicate the data over to it on the > original server. After slony replicating over to the freshly initdb'd original server, the problem has not recurred. Maybe the problem was catalog corruption? -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #6622: ld.so.1: initdb: fatal: libxsit.so.1: open failed: No such file or directory
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 Support, I need assistance in trying to create the cluster. I'm not sure if this is an OS issue missing libraries or just a configuration issue. Please advise what the next course of action should be. initdb -D /u01/app/postgres/postgres_data ld.so.1: initdb: fatal: libxslt.so.1: open failed: No such file or directory Killed -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] log_collector doesn't respond to reloads
>> 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 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 have a bugtracker to put it in so the next time someone is working on the log collector for other reasons they can tweak this too, or when some new hacker wants an easy first patch. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6622: ld.so.1: initdb: fatal: libxsit.so.1: open failed: No such file or directory
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 instinct was to suggest checking with ldd; but since I don't know much about Solaris I did a web search. You might find this thread helpful for trouble-shooting techniques: http://www.linuxquestions.org/questions/solaris-opensolaris-20/httpd-fatal-libpng12-so-0-open-failed-no-such-file-or-directory-893924/ -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] log_collector doesn't respond to reloads
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 have a > bugtracker to put it in so the next time someone is working on the log > collector for other reasons they can tweak this too, or when some new > hacker wants an easy first patch. We have that; it's called TODO. http://wiki.postgresql.org/wiki/Todo regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
