Open ZeyadYasser opened 1 year ago
This has now been fixed in the main branch. Sorry about this
@toluaina Thank you!
@toluaina we have exactly the same issue. Is it possible to release a new version so we can check that out with pip
in our Dockerfile
?
In any case, the command below works in the meantime:
pip install pip install https://github.com/toluaina/pgsync/archive/main.zip
PGSync version: 2.5.0
Postgres version:
Elasticsearch version:
Redis version:
Python version: 3.8
Problem Description: The problem happens when running bootstrap command using a newer version of PGSync for an existing PGSync setup.
The problem was introduced by a new version of PGSync specifically this commit. It forces the check of the columns for the internal materialized view it created
public._view
.Older versions of PGSync didn't have the
indices
column in the materialized view. Theindices
column was introduced on 13/12/2022, in this commit.PGSync is not taking into account existing materialized views it created without the
indices
column (i.e. not backward compatible). This is a bug because the check runs and raises the exception (inSync
object init function) before bootstrap process gets to drop/create the materialized view with the correct column.Error Message (if any):
A quick fix for me and for anyone facing the same problem was locking PGSync to version 2.3.3 (i.e before the
indices
column was introduced)Thank you!