Yoann La Cancellera
Yoann La Cancellera
Found it. It was a permission issue on pgbouncer schema. The error is obfuscated unfortunately, it would be really nice to display it as pgbounceruser was getting a proper "permission...
Why not actually, it would be fun, I will try over the next days
Here is the actual code That's the main: https://github.com/percona/percona-toolkit/blob/v3.5.7/src/go/pt-galera-log-explainer/main.go That's a subcommand: https://github.com/percona/percona-toolkit/blob/v3.5.7/src/go/pt-galera-log-explainer/list.go Other subcommand will have "Paths" as well And in usage it look like `pt-galera-log-explainer list --all *.log`,...
For the record: not sure if that's a better solution, though it's possible to use ``` for _, path := range kongcli.Path { if path.Positional != nil && path.Positional.Name ==...
Missed your initial update sorry! > I think it might be a good idea to wait for the release. What do you think? Yes definitely it will be easier then....
This is just because it's one of the potential reason that could explain a wraparound/vacuum issue: it can hoard row versions So having xmin associated to prepared txs can give...
Actually yes, having the oldest xmin age and when it was prepared in findings seems more than enough