PITR Document link

https://www.percona.com/doc/kubernetes-operator-for-pxc/backups.html#storing-binary-logs-for-point-in-time-recovery

Issue 1: 

`type` key can be equal to one of the following options, * date - roll back to specific date, * transaction - roll back to specific transaction, * latest - recover to the latest possible transaction

comment:

1. There's one more type supported since 1.7.0, * skip - skip a specific transaction https://github.com/percona/percona-xtradb-cluster-operator/blob/v1.7.0/cmd/pitr/recoverer/recoverer.go#L192

2. type * transaction is added start from 1.8.0

Issue 2:

{{}}

• `gtidSet` key is used with type=transaction option - it contains exact GTID or GTIDSet (the restore will not include the transaction with specified GTID, but the one before it)

Comment:

• `gtidSet` key is only for 1.7.0, as of 1.8.0, `gtid` is used instead, it contains an exact GTID (the restore will not include the transaction with specified GTID, but the one before it)

https://github.com/percona/percona-xtradb-cluster-operator/blob/v1.7.0/cmd/pitr/recoverer/recoverer.go#L41

https://github.com/percona/percona-xtradb-cluster-operator/blob/v1.8.0/cmd/pitr/recoverer/recoverer.go#L45