Question 1

How to use Noisia with Docker to test PostgreSQL deadlocks?

Accepted Answer

Run 'docker run --rm -ti lesovsky/noisia:latest noisia --help' to see options, then execute with the deadlocks workload. The README provides Docker examples for quick testing in isolated environments.

Question 2

Noisia vs pgbench for PostgreSQL stress testing – which is better?

Accepted Answer

Noisia simulates harmful scenarios like deadlocks and connection exhaustion for resilience testing, while pgbench focuses on transaction performance benchmarking. Use Noisia for failure simulation and pgbench for throughput metrics.

Question 3

Can Noisia be used in production databases?

Accepted Answer

No, the README explicitly warns against it, stating it's for testing only. Reckless usage can cause problems such as connection exhaustion or accidental backend termination, so always use in controlled environments.

Question 4

How to integrate Noisia into a Go application for automated testing?

Accepted Answer

Import the noisia package, configure workloads like waitxacts with contexts to control execution, as shown in the code example. This allows embedding stress tests into CI/CD pipelines or custom scripts.

Question 5

What are the risks of running Noisia on a live database?

Accepted Answer

Risks include exhausting max_connections, causing table and index bloat, terminating active backends, and blocking queries, as detailed in the workload impact table. Always test in isolated staging setups.

Question 6

Does Noisia support simulating specific query patterns for stress testing?

Accepted Answer

No, it uses predefined workloads; for custom patterns, you'd need to modify the Go source code or use other tools. The built-in help lists available options like idle transactions or rollbacks.

Noisia

What is Noisia?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions