RE: Recovery performance of standby for multiple concurrent truncates on large tables

From: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
To: 'Andres Freund' <andres(at)anarazel(dot)de>
Cc: "Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com>, "'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:55:36
Message-ID: 0A3221C70F24FB45833433255569204D1FA753DD@G01JPEXMBYT05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: 'Andres Freund' [mailto:andres(at)anarazel(dot)de]
> I'm continuing to work on it, but unfortunately there's a couple
> projects that have higher priority atm :(. I'm doubtful I can have a
> patchset in a committable shape for v12, but I'm pretty sure I'll have
> it in a shape good enough to make progress towards v13. Sorry :(

We'd like to do it for PG 12, if Kirk's current proposal doesn't find a good landing point. Could you tell us about how many lines of code you predict, and what part would be difficult? Is there any software you're referring to (e.g. Linux's fsync, MySQL, etc.)?

Regards
Takayuki Tsunakawa

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-07-31 07:03:32 Re: Speeding up INSERTs and UPDATEs to partitioned tables
Previous Message Tsunakawa, Takayuki 2018-07-31 05:44:03 RE: Recovery performance of standby for multiple concurrent truncates on large tables