Re: pg_dump fails with socket_not_open
От | Tom Lane |
---|---|
Тема | Re: pg_dump fails with socket_not_open |
Дата | |
Msg-id | 8200.1111341886@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pg_dump fails with socket_not_open (Sarah Ewen <sarah@thaum.net>) |
Список | pgsql-general |
Sarah Ewen <sarah@thaum.net> writes: >> Is this repeatable? What shows up in the postmaster's log when it >> happens? What platform is this on, and what version of Postgres? > This is postgresql-7.4.6-1.FC2.2 running on RedHat Fedora Core 2. > The logs don't reveal anything, and it happens consistently! The 7.4 RPMs' startup script sends the postmaster stderr to /dev/null :-(. To find out what the server sees as the problem, you need to either hack the startup script to send stderr someplace more useful, or adjust the configuration to send the postmaster's log messages to syslog. I would recommend doing one or the other since it's quite likely that the server-side view of the problem is different from what the client sees. > It is a little disconcerting..by the sounds of things this is a fairly > rare thing to see? Yes. I would like to get to the bottom of it. regards, tom lane
В списке pgsql-general по дате отправления: