Unsupported Database issue after upgrade to V18

[g.fiszt]

Hello everyone!

I've made the upgrade from V16 to V18 and it's completed smoothly.
We have a slave PostgreSQL database that we make queries and the results are displayed in some custom dashboards that we created on Google DataStudio.

After upgrading to V18, the databases were out of sync, then we upgraded the slave server to Debian 10 and the PostgreSQL to V11 as well and the sync started working again.
The problem is that even with the databases in sync, there are some infos not present in the slave database, thus our dashboards are incomplete. It's more than one table, but for example, the table "callcent_queuecalls" doesn't have newer records after the upgrade.

Was there a change in the database structure from V16 to V18? Or am I forgetting something that I should've done?

 

[cobaltit]

3CX does not support touching the database in any way but if you've setup a slave already, you should be able to browse the database to see if there are changes.

 

[g.fiszt]

I was looking in the slave database and the structure looks like the same.
I guess I'll have to reconfigure the sync. Thanks

 

[g.fiszt]

I was wondering... When you say that we can't touch the database, you're talking about making changes to it, right?
Can I create an user just to make select queries in order to collect the data? Or even that could jeopardize the 3cx database?

 

[ChrisC_3CX]

To be absolutely clear, from the moment the database is accessed, even if it's only for viewing purposes, support will automatically be voided. Consider that viewing may not necessarily mean you're making changes, but it will impede the database/certain tasks and generally affect system performance.