| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Robert Haas' <robertmhaas(at)gmail(dot)com> |
| Cc: | "Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Recovery performance of standby for multiple concurrent truncates on large tables |
| Date: | 2018-07-31 05:44:03 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1FA753AA@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Robert Haas [mailto:robertmhaas(at)gmail(dot)com]
> It's not clear to me whether it would be worth the overhead of doing
> something like this.
Quite frankly, not really to me, too.
> Making relation drops faster at the cost of
> making buffer cleaning slower could be a loser.
The purpose is not making relation drops faster (on the primary), but keeping failover time within 10 seconds. I don't really know how crucial that requirement is, but I'm feeling it would be good for PostgreSQL to be able to guarantee shorter failover time.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tsunakawa, Takayuki | 2018-07-31 05:55:36 | RE: Recovery performance of standby for multiple concurrent truncates on large tables |
| Previous Message | Kyotaro HORIGUCHI | 2018-07-31 04:39:07 | Re: Temporary tables prevent autovacuum, leading to XID wraparound |