bugfix: scope partition maintenance to target table and lock create path

[somethingwithproof]

Summary

• scope partition create/check/remove queries to the requested table instead of hardcoded syslog
• add a table allowlist guard for partition maintenance helpers
• serialize partition creation using GET_LOCK/RELEASE_LOCK to avoid concurrent duplicate partition creation
• add regression test for table scoping and lock usage
• update changelog with issue bug: partition existence check hardcodes table name 'syslog', breaks syslog_removed and allows race condition #254

Fixes #254

Validation

• php -l functions.php
• php -l tests/regression/issue254_partition_table_locking_test.php
• php tests/regression/issue254_partition_table_locking_test.php

[Copilot]

Pull request overview

Fixes syslog partition maintenance so it correctly targets the requested table (e.g., syslog_removed), adds a guardrail for which tables are eligible for partition operations, and serializes partition creation to avoid concurrent “duplicate partition” errors.

Changes:

• Scope information_schema.partitions checks/removals to the $table argument instead of hardcoding syslog.
• Add syslog_partition_table_allowed() allowlist and use MySQL GET_LOCK/RELEASE_LOCK to serialize partition creation.
• Add a regression test that verifies table scoping, lock usage, and the presence of the allowlist helper; update changelog for #254.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
functions.php	Scopes partition queries to the target table, adds allowlist guard, and adds locking around partition creation.
tests/regression/issue254_partition_table_locking_test.php	Adds a regression check ensuring table scoping and lock acquisition/release are present.
CHANGELOG.md	Records the fix for issue #254 under the develop section.