Re: Optimising compactify_tuples()
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndquadrant.com>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Peter Geoghegan <pg@bowt.ie>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-09-16T18:54:24Z
Lists: pgsql-hackers
On Thu, 10 Sep 2020 at 14:45, David Rowley <dgrowleyml@gmail.com> wrote: > I've also attached another tiny patch that I think is pretty useful > separate from this. It basically changes: > > LOG: redo done at 0/D518FFD0 > > into: > > LOG: redo done at 0/D518FFD0 system usage: CPU: user: 58.93 s, > system: 0.74 s, elapsed: 62.31 s > > (I was getting sick of having to calculate the time spent from the log > timestamps.) I really like this patch, thanks for proposing it. Should pg_rusage_init(&ru0); be at the start of the REDO loop, since you only use it if we take that path? -- Simon Riggs http://www.2ndQuadrant.com/ Mission Critical Databases
Commits
-
Optimize compactify_tuples function
- 19c60ad69a91 14.0 landed
-
Report resource usage at the end of recovery
- 10a5b35a0061 14.0 landed
-
Allow incremental sorts for windowing functions
- 62e221e1c01e 14.0 cited