xtstat fails if no PBXT table has been created
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PBXT |
Fix Committed
|
Undecided
|
Paul McCullagh |
Bug Description
Running xtstat on a system with no PBXT table leads to the following error:
$ bin/xtstat --user=root --display=all
Unknown database 'pbxt'
xtstat exits immediately.
Running the following:
$ bin/xtstat --user=root --display=all --database=
Makes PBXT enter a loop, printing the system parameters.
Suggested fixes:
1. When the pbxt.statistics table does not exist, xtstat, should wait until it is created, and then continue.
2. If the pbxt.statistics table does not exist, then it should be created on the first access.
3. The option --database=
As an alternative to 2, it would be possible to switch automatically to information_
Changed in pbxt: | |
assignee: | nobody → Paul McCullagh (paul-mccullagh) |
status: | New → In Progress |
xtstat now accepts --database= information_ schema or --database=pbxt. Depending on this setting PBXT will either use the information_ schema. pbxt_statistics or the pbxt.statistics table. If information_schema is used, then the statistics are displayed even when no PBXT table exists. Recovery activity is also displayed, unless pbxt_support_xa=1, in which case MySQL will wait for PBXT recovery to complete before allowing connections.