GoodData does not use PostgreSQL logical replication for data ingestion. Instead, GoodData connects directly to your PostgreSQL database and issues SQL SELECT queries to retrieve data. Analytical queries are executed live against your data source; there is no ETL process or data ingestion into GoodData itself. The platform queries your database as needed to compute analytics and visualizations, and these queries can be observed in your database logs as standard SQL SELECT statements. GoodData does not automatically poll for changes or only fetch deltas; it queries the data as required for reports, dashboards, or user actions. The queries fetch the data needed for the current analytical request, not just the changes since the last query. Caching mechanisms (such as FlexCache) may store query results to improve performance, but when a query is executed, it retrieves the necessary data from your database at that moment, not just incremental changes. You can also configure the system to bypass the cache and always query live data if real-time updates are required [Connect Data](
https://www.gooddata.com/docs/cloud/connect-data/) [Cache Management](
https://www.gooddata.com/docs/cloud/connect-data/cache-management/) [Community Slack](
https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1723066442966569?thread_ts=1723066442.966569&cid=C04S1MSLEAW). In summary: - GoodData uses SELECT queries, not logical replication. - It does not only grab changes; it queries the data needed for each analytical request. - You can control caching behavior, but there is no built-in incremental/delta-only polling mechanism.