dbt2
Overview
| Package | Version | Category | License | Language |
|---|---|---|---|---|
dbt2 | 0.61.7 | LANG | Artistic-2.0 | C |
| ID | Extension | Bin | Lib | Load | Create | Trust | Reloc | Schema |
|---|---|---|---|---|---|---|---|---|
| 3220 | dbt2 | No | Yes | No | Yes | No | Yes | - |
Package/source version 0.61.7; SQL extension version 0.45.0. This package contains the PostgreSQL stored-function extension, not the full DBT-2 benchmark toolchain.
Version
| Type | Repo | Version | PG Ver | Package | Deps |
|---|---|---|---|---|---|
| EXT | MIXED | 0.61.7 | 1817161514 | dbt2 | - |
| RPM | PGDG | 0.61.7 | 1817161514 | dbt2-pg$v-extensions | - |
| DEB | PIGSTY | 0.61.7 | 1817161514 | postgresql-$v-dbt2 | - |
Build
You can build the DEB packages for dbt2 using pig build:
Install
You can install dbt2 directly. First, make sure the PGDG and PIGSTY repositories are added and enabled:
Install the extension using pig or apt/yum/dnf:
Create Extension:
Usage
dbt2 is a TPC-C benchmark implementation for PostgreSQL. The extension provides stored procedures that implement the five standard TPC-C transaction types.
TPC-C Transaction Types
The extension provides stored procedures for the five standard TPC-C transactions:
- New Order: Creates a new order with multiple line items, updating stock levels
- Payment: Processes a customer payment, updating warehouse and district balances
- Order Status: Retrieves the status of a customer’s most recent order
- Delivery: Processes pending orders for delivery across all districts
- Stock Level: Checks the count of recently sold items with low stock
Benchmark Workflow
The dbt2 system consists of:
- Database extension (
dbt2): Stored procedures for TPC-C transactions - Data loader: Populates the benchmark tables with TPC-C data
- Driver: Generates transaction workloads simulating terminal users
- Client: Manages connections between the driver and database
Running Benchmarks
The benchmark is typically run using the dbt2 command-line tools (separate from the extension):
TPC-C Schema
The benchmark uses these standard tables: warehouse, district, customer, history, new_order, orders, order_line, item, and stock.
Refer to the doc/ directory in the repository for detailed configuration and tuning options.
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)