proxysql

Commit Graph

Author	SHA1	Message	Date
Rene Cannao	ab7d9187cb	test(pgsql-eventslog): improve autodump assertion diagnostics and runtime cleanup Test diagnostics: - Add explicit `diag()` output for successful-row assertion failures. - Include expected row count, observed row count, and query status for faster CI triage. Cleanup behavior: - Extend cleanup to restore: - `pgsql-eventslog_default_log=0` - `pgsql-eventslog_buffer_history_size=0` - Apply both runtime loads during cleanup: - `LOAD ADMIN VARIABLES TO RUNTIME` - `LOAD PGSQL VARIABLES TO RUNTIME` This avoids residual PGSQL eventslog settings leaking into subsequent TAP tests.	4 months ago
Rene Cannao	2586995478	tap(pgsql): add end-to-end test for eventslog automatic buffer-to-disk sync Context: - PostgreSQL advanced query logging already had end-to-end coverage for manual dump flows. - Scheduler-driven automatic dump path also needs explicit TAP coverage. Test added: - `test/tap/tests/pgsql_query_logging_autodump-t.cpp` - Connects to PGSQL admin and frontend interfaces. - Enables query logging and admin scheduler variable: `admin-stats_pgsql_eventslog_sync_buffer_to_disk=1` - Generates frontend workload (`SELECT 1` loop). - Polls `history_pgsql_query_events` to assert rows are flushed to disk by scheduler. - Validates successful rows are present (`sqlstate IS NULL`). - Restores scheduler variable to `0` during cleanup. Harness wiring: - Register `pgsql_query_logging_autodump-t` in `test/tap/groups/groups.json` so it runs with default PGSQL test group settings. Why: - Close e2e coverage gap between manual dump and auto-dump behavior for PGSQL events logging. - Catch regressions in scheduler-based buffer synchronization path.	4 months ago

Author

SHA1

Message

Date

Rene Cannao

ab7d9187cb

test(pgsql-eventslog): improve autodump assertion diagnostics and runtime cleanup

Test diagnostics:
- Add explicit `diag()` output for successful-row assertion failures.
- Include expected row count, observed row count, and query status for faster CI triage.

Cleanup behavior:
- Extend cleanup to restore:
  - `pgsql-eventslog_default_log=0`
  - `pgsql-eventslog_buffer_history_size=0`
- Apply both runtime loads during cleanup:
  - `LOAD ADMIN VARIABLES TO RUNTIME`
  - `LOAD PGSQL VARIABLES TO RUNTIME`

This avoids residual PGSQL eventslog settings leaking into subsequent TAP tests.

Rene Cannao

2586995478

tap(pgsql): add end-to-end test for eventslog automatic buffer-to-disk sync

Context:
- PostgreSQL advanced query logging already had end-to-end coverage for manual dump flows.
- Scheduler-driven automatic dump path also needs explicit TAP coverage.

Test added:
- `test/tap/tests/pgsql_query_logging_autodump-t.cpp`
  - Connects to PGSQL admin and frontend interfaces.
  - Enables query logging and admin scheduler variable:
    `admin-stats_pgsql_eventslog_sync_buffer_to_disk=1`
  - Generates frontend workload (`SELECT 1` loop).
  - Polls `history_pgsql_query_events` to assert rows are flushed to disk by scheduler.
  - Validates successful rows are present (`sqlstate IS NULL`).
  - Restores scheduler variable to `0` during cleanup.

Harness wiring:
- Register `pgsql_query_logging_autodump-t` in `test/tap/groups/groups.json` so it runs with default PGSQL test group settings.

Why:
- Close e2e coverage gap between manual dump and auto-dump behavior for PGSQL events logging.
- Catch regressions in scheduler-based buffer synchronization path.

2 Commits (mysqlx-plugin-impl)