Error with prepared statements in Airbyte on GKE with self-deployed Postgres

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is encountering errors related to prepared statements in Airbyte deployed on GKE with self-deployed Postgres. Despite trying to disable pg_bouncer and setting binary_parameters to yes in the jdbc, the issue persists. Data synchronization between source and sink is working fine.


Question

Hi, I have deployed Airbyte on GKE with self-deployed Postgres instead of using Postgres of Airbyte. I am getting the following errors in the temporal pod-

	/home/builder/temporal/common/log/zap_logger.go:150
go.temporal.io/server/common/persistence.updateErrorMetric
	/home/builder/temporal/common/persistence/persistenceMetricClients.go:1171
go.temporal.io/server/common/persistence.(*metricEmitter).recordRequestMetrics
	/home/builder/temporal/common/persistence/persistenceMetricClients.go:1148
go.temporal.io/server/common/persistence.(*executionPersistenceClient).GetHistoryTasks.func1
	/home/builder/temporal/common/persistence/persistenceMetricClients.go:371
go.temporal.io/server/common/persistence.(*executionPersistenceClient).GetHistoryTasks
	/home/builder/temporal/common/persistence/persistenceMetricClients.go:373
go.temporal.io/server/common/persistence.(*executionRetryablePersistenceClient).GetHistoryTasks.func1
	/home/builder/temporal/common/persistence/persistenceRetryableClients.go:366
go.temporal.io/server/common/backoff.ThrottleRetryContext
	/home/builder/temporal/common/backoff/retry.go:199
go.temporal.io/server/common/persistence.(*executionRetryablePersistenceClient).GetHistoryTasks
	/home/builder/temporal/common/persistence/persistenceRetryableClients.go:370
go.temporal.io/server/service/history/queues.NewImmediateQueue.func1.1
	/home/builder/temporal/service/history/queues/queue_immediate.go:79
go.temporal.io/server/common/collection.(*PagingIteratorImpl[...]).getNextPage
	/home/builder/temporal/common/collection/pagingIterator.go:116
go.temporal.io/server/common/collection.NewPagingIterator[...]
	/home/builder/temporal/common/collection/pagingIterator.go:52
go.temporal.io/server/service/history/queues.(*IteratorImpl).HasNext
	/home/builder/temporal/service/history/queues/iterator.go:71
go.temporal.io/server/service/history/queues.(*SliceImpl).SelectTasks
	/home/builder/temporal/service/history/queues/slice.go:375
go.temporal.io/server/service/history/queues.(*ReaderImpl).loadAndSubmitTasks
	/home/builder/temporal/service/history/queues/reader.go:434
go.temporal.io/server/service/history/queues.(*ReaderImpl).eventLoop
	/home/builder/temporal/service/history/queues/reader.go:403", "ts":"2024-01-05T05:04:43.504Z"}```
I am getting more such errors regarding prepared statements. I have tried disabling pg_bouncer and setting `binary_parameters=yes` in the jdbc, but, still facing the same issues. Data is synced between the source and sink destination perfectly fine. But, still getting this error. Any idea what is the issue?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1704432092637539) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["error", "prepared-statements", "airbyte", "gke", "self-deployed-postgres", "pg-bouncer", "binary-parameters", "data-synchronization"]
</sub>