By Chason ArthurRevision 127.036Published Updated

PostgreSQL / Analytics / Data correctness

Run it. Change it. Verify it.

Start in your browser, then take the complete SQL Reporting Lab into an independent local environment.

Try it without installing a toolchain

  1. Open the playground and keep its default scenario.
  2. Run the comparison and read the results before opening the code.
  3. Change the scenario, run again, and identify which decision changed.
  4. Open View the code, choose a source file and read the explanation above it.
  5. Reset the environment, including a run that is still pending.
Open the playground

Run your downloaded copy

Download and extract the ZIP into a new folder. With Python 3 installed, open a terminal in that folder and run the command below. It serves only this package on loopback; opening index.html directly is insufficient for workers and WebAssembly.

python preview.py

Open http://127.0.0.1:4210/ in your browser. Stop the server with Ctrl+C. The prebuilt preview needs no dependency installation and makes no automatic requests to another site. The source code and notices are included alongside it.

Run the native exercise

The commands below start in the extracted package root. Node-based examples require Node 24 or later; the Go adapter requires Go 1.27 or later; the Python adapter requires Python 3.11 or later. Install only the toolchain used by this lab. Exact dependency versions and the Node lockfile are in the download.

npm ci
npm test
npm run rebuild
python preview.py

Revenue is 42000 cents with the multiplying join and 30000 at order grain. The local-day example returns 26000 cents; the UTC-day query returns 24000. The safeguarded cohort has one A user and two B users.

Read GETTING_STARTED.md for the native request examples and shutdown steps. Native servers bind to 127.0.0.1. The optional monitoring containers expose only loopback ports. They are a separate exercise from the browser preview.

Make one meaningful change

Add two distinct orders with the same amount and demonstrate why SUM(DISTINCT amount_cents) is an invalid fanout repair. Then define a late-arrival cutoff and keep that policy fixed while comparing implementations.

Add the expected result first, reproduce the failure, repair it, then rerun the native and browser checks. Use npm run rebuild for the Node/browser examples. The Go package includes rebuild_wasm.py; the Python package includes refresh_source.py.

Record what you learned

Capture the scenario, edition, input records, observed outcome and the test that checks it. Explain one alternative you rejected and why. Avoid converting a small local result into a throughput, security or accuracy claim about a production system.

Read the primary documentation

Rebuy’s staff role calls for accurate experimentation reports, data models and analytical queries.

Related role from the job review

Choose your next step

Build the safeguards

Eight explained steps, a source example and a checkpoint at each decision.

Read the tutorial

Compare the alternatives

Understand where each pattern helps and which tradeoffs remain.

Compare approaches

Run and extend it locally

Download the independent environment, run the native checks and try a specific extension.

Open the how-to guide