Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Looking for a list of confluence table names in postgres Edited

Hi,

I am trying to convert my database from mysql to postgres. And I see in postgres some tables are expected to be lower case and some are in higher case.

Example: 

BANDANA is higher case in MySQL, but expected in lowercase in postgres.

SECRETS is higher case in MySQL and also expected in higher case in postgres. 

So the problem is the casing is not consistent and hence, I am unable to add any rules in pgloader to do my transformations properly. Atleast according to this article: https://developer.atlassian.com/server/framework/atlassian-sdk/table-names/, upper case names are expected for PLUGIN data related tables.

One way I may be able to fix this is try to start confluence and follow errors and fix table name cases accordingly one by one. But I want to know if there is already a list of table and column names with expected case for postgres db?

Also, I tried pgloader in two settings:

1. With default settings, where it does most of the conversions as confluence expects in postgres. (I think it could be a bug in atlassian side where it uses doublequotes on tables not related to plugins and are expected in higher case. Example: SECRETS)

2. quoted_identfiers, where it retains the mysql casing. In this, I found most of the tables have wrong casing.

So, pgloader default settings maybe good starting point. 

Or please tell me if I am doing anything wrong or if there is another way to fix this.

We want this migration to be done successfully, so that we can switch to datacenter solution where postgres can scale well. 

1 answer

Looks like only synchrony tables are names are converted wrongly with pglaoder default settings: SNAPSHOTS, SECRETS, EVENTS -> all lower cased with default settings of pgloader.

I don't see errors with any other tables so far.

However, there are many duplicated tables created. So I think I can use these duplicated tables list to add conditions in pgloader

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

159 views 2 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you