Re: pg_upgrade --logfile option documentation
От | Robert Haas |
---|---|
Тема | Re: pg_upgrade --logfile option documentation |
Дата | |
Msg-id | CA+Tgmoa4L8M7J-L+ntVOy-sQ5=GDWo4CSLppw6-bWWA68XwYzw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_upgrade --logfile option documentation (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: pg_upgrade --logfile option documentation
Re: pg_upgrade --logfile option documentation |
Список | pgsql-hackers |
On Wed, Feb 29, 2012 at 6:02 PM, Bruce Momjian <bruce@momjian.us> wrote: >> Any ideas about improving the error reporting more generally, so that >> when reloading the dump fails, the user can easily see what went >> belly-up, even if they didn't use -l? > > The only idea I have is to write the psql log to a temporary file and > report the last X lines from the file in case of failure. Does that > help? Why not just redirect stdout but not stderr? If there are error messages, surely we want the user to just see those. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: