YugabyteDB has support for most of the constructs used by pgloader. For some that are not yet supported, we can have alternate implementation and code paths specific to YugabyteDB to make it work.
There could be some use cases that will not work due to unsupported features in YugabyteDB, we can fail gracefully with a warning.
Some of the alternate ways to handle YugabyteDB are listed here and have been tried to make it work:
yugabyte/yugabyte-db#7886
We should try to make the changes on the lines of Redshift where the code path specific to YugabyteDBs are executed depending on the version string.
If the community has an interest, we can raise the pull request so that migrating the database to YugabyteDB is natively supported by pgloader.
YugabyteDB has support for most of the constructs used by pgloader. For some that are not yet supported, we can have alternate implementation and code paths specific to YugabyteDB to make it work.
There could be some use cases that will not work due to unsupported features in YugabyteDB, we can fail gracefully with a warning.
Some of the alternate ways to handle YugabyteDB are listed here and have been tried to make it work:
yugabyte/yugabyte-db#7886
We should try to make the changes on the lines of Redshift where the code path specific to YugabyteDBs are executed depending on the version string.
If the community has an interest, we can raise the pull request so that migrating the database to YugabyteDB is natively supported by pgloader.