Errors or warnings appear when importing Postgres database dump

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

問題

When importing a Postgres database dump from a Bamboo Cloud export, errors or warnings such as the following appear:

ERROR:  relation "public.plan_dependencies" does not exist
ERROR:  index "vrs_status_idx" does not exist
ERROR:  table "AO_C7F71E_OAUTH_SVC_PROV_TKNS" does not exist
ERROR:  sequence "AO_A0B856_WEB_HOOK_LISTENER_AO_ID_seq" does not exist
ERROR:  must be owner of language plpgsql
ERROR:  must be owner of schema public
ERROR:  schema "public" already exists
ERROR:  language "plpgsql" already exists
ERROR:  role "bamboo_ro"
WARNING:  no privileges could be revoked for "public"
WARNING:  no privileges were granted for "public"

Note: if you see the following errors (note the numbers after the user) instead, you've run into a different issue:

ERROR: role "bamboo_12345" does not exist
ERROR: role "bamboo_12345" does not exist
ERROR: role "bamboo_ro_12345_1" does not exist

(where 12345 may be any random string of numbers). If you see these errors, please instead follow the steps listed on  BAM-18060 - Getting issue details... STATUS

原因

When importing a db dump into Postgres, it will try to remove any existing data from the destination database to ensure a clean import. If the destination database is empty, these errors and warnings will appear.

ソリューション

This is expected behaviour during an import of a database dump and can safely be ignored.

Note: If you see errors different from the examples listed above, you should contact Atlassian Support

 

最終更新日: 2016 年 12 月 21 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.