Alexander Evseev

Results 12 comments of Alexander Evseev

MySQL CI -> PostgreSQL collation-dependent varchar primary keys result in 'Duplicate key value violates unique constraint'

> Could you please paste in the full CREATE TABLE statements for both source and destination databases, and also check what character set and collation is default for both source...

MySQL CI -> PostgreSQL collation-dependent varchar primary keys result in 'Duplicate key value violates unique constraint'

MySQL: ``` | character_set_database | utf8 | | collation_database | utf8_general_ci | ``` Create table statement (see above) specifies only charset - utf8. PostgreSQL database has charset UTF8 and collation/ctype...

MySQL CI -> PostgreSQL collation-dependent varchar primary keys result in 'Duplicate key value violates unique constraint'

I've checked source (MySQL) table - there is no id's similar to the problematic one.

MySQL CI -> PostgreSQL collation-dependent varchar primary keys result in 'Duplicate key value violates unique constraint'

Sorry, can't check. I've added "drop schema; create schema" on the target DB (PG) and and KS runs successfully. I.e. sync succeeds if there is no tables/data in target DB...

MySQL CI -> PostgreSQL collation-dependent varchar primary keys result in 'Duplicate key value violates unique constraint'

> What version of PostgreSQL are you using? We're using PostgreSQL 12 at destination

[bitnami/oauth2-proxy] Add DNS parameters to the oauth2 deployment

I've changed original commit to bump chart version

Cannot apply CRD and a CR using it in the same plan/apply due to SSA

I've found a solution to have the only manifest, but it should be run twice: ``` resource "helm_release" "cert_manager" { name = "cert-manager" chart = "cert-manager" repository = "https://charts.jetstack.io" namespace...

Consolidation job ignores Next/Full Backup Pool

I've added `Virtual Full Backup Pool = pool-1-2` to job `Artifactory Backup`, and got the same error. I didn't new full/incremental backups (just updated job `Artifactory Backup`, reloaded config, and...

Consolidation job ignores Next/Full Backup Pool

Tried one more time only having `Next Pool = pool-1-2` in `Artifactory Backup` and it works. I think you may close the issue. Looks like I missed something. Sorry.

Consolidation job ignores Next/Full Backup Pool

Looks like `Next Pool` should work always: https://github.com/bareos/bareos/blob/bdb86e83b4736033956f9d6ef1d1498cf43c0a40/core/src/dird/vbackup.cc#L171