pgbench[2] / pgreplay-go[0] / python locust[1] very old school approach: Misuse sql VIEW[3][4] to generate a temporary parallel table setup. Testing database

pgbench[2] / pgreplay-go[0] / python locust[1] very old school approach: Misuse sql VIEW[3][4] to generate a temporary parallel table setup. Testing database separate from production database would be 'better', IMHO. ----- [0] pgreplay-go : https://github.com/gocardless/pgreplay-go https://github.com/gocardless/pgreplay-go [1] python locust : https://miguel-codes.medium.com/unconventional-load-testing-leveraging-python-locust-for-postgresql-stress-testing-d6e07d63714b https://miguel-codes.medium.com/unconventional-load-testing-... [2] pgbench load testing : a) https://medium.com/@c.ucanefe/pgbench-load-test-166bdfb5c75a b) https://neon.tech/blog/autoscaling-in-action-postgres-load-testing-with-pgbench c) https://hackernoon.com/how-to-create-and-load-test-data-in-postgresql-i41e353m ---------------------------- [3] : a) https://hashrocket.com/blog/posts/materialized-view-strategies-using-postgresql https://hashrocket.com/blog/posts/materialized-view-strategi... b) https://tech.jonathangardner.net/wiki/PostgreSQL/Materialized_Views c) https://stackoverflow.com/questions/77603705/what-is-the-use-of-materialized-view-in-postgresql [4] : https://en.wikipedia.org/wiki/View_(SQL) https://en.wikipedia.org/wiki/View_(SQL)