Re: pg_group_name_index corrupt?
| От | Tom Lane |
|---|---|
| Тема | Re: pg_group_name_index corrupt? |
| Дата | |
| Msg-id | 9265.957589558@sss.pgh.pa.us обсуждение |
| Ответ на | Re: pg_group_name_index corrupt? (Tatsuo Ishii <t-ishii@sra.co.jp>) |
| Ответы |
Re: pg_group_name_index corrupt?
|
| Список | pgsql-hackers |
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> (BTW is it really possible for postmaster to remember its process
> priority?)
No, but a site might have a startup script that nice's the postmaster
to a desired priority.
> BTW, currently the best way to get logs from postmaster woul be
> compiling it with USE_SYSLOG (why is this not enabled by configure?),
Good question. Before we standardize on that, however, some testing
might be in order. I haven't tried stuffing multimegabyte querytree
dumps into syslog ... will it work? On how many platforms? The syslog
applications I've seen never write more than a hundred or so characters
per log entry, so I'm a tad nervous about assuming that we will get
reasonable behavior for large messages...
regards, tom lane
В списке pgsql-hackers по дате отправления: