postgres
The migration to v2 finished without errors. However my database wasn't migrated.
Trying to back it up and restore with pgAdmin failed due to a timescale issue.
Any suggestions how I can get my DB migrated?
21 Replies
Project ID:
102ec349-3da6-4a1e-bee3-4bcd2cec0e73this is the serviceId: 102ec349-3da6-4a1e-bee3-4bcd2cec0e73
the legacy database has the timescale extension and so does the database that the migration process deploys.
are you saying that the database created by the migration process is missing data?
it asked for a project id
only the prostgres and railway dbs migrated
my DB didn'y migrate
what specific database was not migrated
project id : 5ccdb93b-0ab6-49ff-a171-1985732f73e1
my db is called routeIt
please tell me the method you used to confirm the missing database in the new postgres service
I connected with pgAdmin
and you where given a list of databases and your
routeIt was not one of them?that is correct. I have since then created so I can restore into it ( again with pgAdmin) but I'm getting a metaData failure
did you use any timescale features on your legacy database?
no
simple tables
if they are simple tables within the database you should be able to just dump only your tables and restore them to the new database
That's what I tried.
It failed
pg_restore: error: COPY failed for table "metadata": ERROR: duplicate key value violates unique constraint "metadata_pkey"
That was the cause for teh failure
However the data was restored.
So I hope it is ok
I'll check my app
you've now confirmed all the data in the new database on the new postgres service?