| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Start background writer during archive recovery. |
| Date: | 2009-02-25 22:52:48 |
| Message-ID: | 3f0b79eb0902251452t38d8d4c0scd3d5092c391bcfa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Hi,
I have two questions about the stats collector during recovery.
1)
Why does the stats collector need to wait for consistent recovery
mode? The activity statistics which bgwriter may send before
reaching the mode should be ignored?
2)
Why doesn't ServerLoop() try to restart the stats collector
when it's not in progress?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Fxjr | 2009-02-26 02:06:58 | npgsql - Npgsql2: Really fixed culture dependent representation of |
| Previous Message | Tom Lane | 2009-02-25 18:00:22 | pgsql: Fix an old problem in decompilation of CASE constructs: the |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-02-25 23:21:20 | effective_cache_size less than shared_buffers |
| Previous Message | Bruce Momjian | 2009-02-25 22:50:07 | Re: Synchronous replication & Hot standby patches |