


SELECT count(*) FROM pgbench_accounts JOIN pgbench_accounts_copy using (aid) * As unique columns joining improvements where mentioned. SELECT sum(abalance) FROM pgbench_accounts CROSS JOIN generate_series(1, 5) * Sum up 50mio row as SUM function was mentioned in the release notes */ Postgres has excellent analytical support, so making a choice on what to test exactly without going through the v10 Git changelog in details caused me halt for a moment, but I thought I’ll keep it simple this time (will hopefully go deeper for the final Release Candidate) and I conjured up 3 quite simple SELECT queries based on the hints from release notes and on the schema generated by our good old friend pgbench. So now I found time to exactly do that and I’m again just laying out the numbers on running some analytical queries for you to evaluate. Release notes stated up to +40% for cases, with large number of rows (which could mean different things to different people of course), with an added note to test it out and report back. Besides the very visible version numbering scheme change (no more X.Y.Z ) the release notes promised amongst other very cool and long-awaited features – like built-in Logical Replication and Table Partitioning – also many performance improvements, especially in the area of analytics. Some weeks ago the Beta 1 of upcoming Postgres 10 was released.
