From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
---|---|
To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [RFC] Should we fix postmaster to avoid slow shutdown? |
Date: | 2016-12-01 13:01:58 |
Message-ID: | CAFjFpRftFzZ+wdnRJ6EbNTcdZkDF5_KVpFAf5NB07LQ41Dy31Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> I also find others's ideas woth considering -- WAL-logging the stats files, type-specific stats files, etc. -- but I'm afraid those ideas would only be employed in a new major release, not in released versions. I'm asking for a remedy for a user (and potential users) who use older releases. And, I don't yet understand why patch would make the situation for existing users, and why stop writing files during immediate/abnormal shutdown requires other efforts.
>
I agree with this. I don't think we are going to change stats file
management in older versions. Hence after every crash recovery they
will be thrown away. In that case, why should stats collector in the
older versions wait for those files to be flushed to the disk? I
think, we should apply patch to shut down stats collector immediately
to the older versions and implement the stats file management solution
to the head. Why isn't that a feasible option?
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2016-12-01 14:06:15 | Re: [HACKERS] postgres 1 个(共 2 个) can pg 9.6 vacuum freeze skip page on index? |
Previous Message | Amit Kapila | 2016-12-01 12:57:26 | Re: Parallel execution and prepared statements |