falcon VS dms-psql-post-data

Regarding visualization tools, sqliteviz has proven to be the best I've found so far. Their web app runs locally but has some trackers, so I run it locally via a simple, static HTTP server. Falcon and Redash seem like overkill for my needs.

As you can see, I have Postgres db running in my container, I also have a client I want to use to access this database (falcon-client), however, it cannot connect to the db, I'm assuming it's because my port at 5432 is not allowing access to the database (as suggested here)

Or maybe Falcon as a desktop tool.

33. Falcon

Fortunately, native tools helped us a lot. To get all the indexes and constraints, we used pg_dump with the --section=post-data option and then inlined the content of the dump and ran it directly from the Postgres console to have better visibility and control of the process. To bring back sequences, we used this script. It was very odd that AWS DMS does not have any option to handle this—it's capable of migrating Oracle to Neptune, yet it's not capable of smoothly handling indexes for the Replication Instance strategy, even though it's a trivial operation.

dms-psql-post-data 방신우 shares this script that may come in hand if you are looking at doing any PostgreSQL-to-PostgreSQL migrations. Why might you need this script? Well, its in the README, but to summarise, this script can help you resolve some artefacts that are not migrated, and if you want to target the migrated database as primary.