harbor/tools/migration/db/schema/notarysigner_alter_tables.pgsql

\c notarysigner;

ALTER TABLE private_keys OWNER TO signer;
ALTER SEQUENCE private_keys_id_seq OWNER TO signer;
ALTER TABLE schema_migrations OWNER TO signer;
Fix unable to use Notary after updating to v1.6.0 This commit is to fix the issue on notary migrations from mysql to pgsql. 1, alter sequence for the primary key of changeseed, this is missed in v1.6.0 migrator. 2, alter table owners from postgres to notarysigner and notaryserver. Issue: https://github.com/goharbor/harbor/issues/6465 Workaround: https://github.com/goharbor/harbor/issues/6465#issuecomment-445162616 Impacted upgrade path: 1, Upgrade from version older then v1.6.0 with migrator:v1.6.0, and migrates the notarty DB. No impacted upgrade path: 1, Upgrade from version older than v1.6.0 with migrator:v1.6.0, but without migrates the notarty DB. Notes： After merge this fix, we need to provide an new migrator with an new tag, like v1.6.1, and deprecated the v1.6.0. For those who was impacted by migrator v1.6.0, will open an new PR to build the workaround into the migrator and expose an specical command for hot-fix. Signed-off-by: wang yan <wangyan@vmware.com> 2018-12-07 09:59:25 +01:00			`\c notarysigner;`

			`ALTER TABLE private_keys OWNER TO signer;`
			`ALTER SEQUENCE private_keys_id_seq OWNER TO signer;`
			`ALTER TABLE schema_migrations OWNER TO signer;`