Hey all, we had meltano running in production succ...
# troubleshooting
m
Hey all, we had meltano running in production successfully to sync psql to psql from a number of source and destinations until a couple of days ago and they all started failing with
Copy code
target-postgres | time=2022-01-31 09:00:10 name=target_postgres level=CRITICAL message=Primary key is set to mandatory but not defined in the [public-pg_stat_statements] stream
target-postgres | Traceback (most recent call last):
target-postgres |   File "/home/meltano/meltano/cdp-posthog-production/.meltano/loaders/target-postgres/venv/bin/target-postgres", line 8, in <module>
target-postgres |     sys.exit(main())
target-postgres |   File "/home/meltano/meltano/cdp-posthog-production/.meltano/loaders/target-postgres/venv/lib/python3.7/site-packages/target_postgres/__init__.py", line 373, in main
target-postgres |     persist_lines(config, singer_messages)
target-postgres |   File "/home/meltano/meltano/cdp-posthog-production/.meltano/loaders/target-postgres/venv/lib/python3.7/site-packages/target_postgres/__init__.py", line 209, in persist_lines
target-postgres |     raise Exception("key_properties field is required")
target-postgres | Exception: key_properties field is required
meltano         | Loading failed (1): Exception: key_properties field is required
meltano         | ELT could not be completed: Loader failed
ELT could not be completed: Loader failed
We haven’t updated the tap or target and the only change we made on the DB was granting access to the public schema but it ran successfully two days after that happened. Any ideas where to start?
Looks like we loaded a new extension that meltano is trying to sync. Trying to work out how to exclude
m
ended up with meltano elt tap-postgres target-postgres --exclude public-pg_stat_statements.*
ty @fred_reimer