From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Igor Polishchuk <ora4dba(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to create logical replication slot with NOEXPORT_SNAPSHOT in jdbc |
Date: | 2018-07-17 11:29:50 |
Message-ID: | 2e397db3-823f-7608-ec98-dc235ccdd105@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 17.07.18 03:41, Igor Polishchuk wrote:
> We are trying to use logical decoding for detecting database changes.
> However, when we create a replication slot, the data processing pauses
> if there are still transactions running from before the slot creation.
> If I understand correctly, the slot is waiting for creating a consistent
> snapshot and is blocked by the long transactions.
> In our application, we don't need it, as we only want to see if some
> tables were modified. Is it possible to create a logical replication
> slot with NOEXPORT_SNAPSHOT option using jdbc?
That doesn't do what you want. You still need to wait for the snapshot
to be created; there is no way around that. The NOEXPORT_SNAPSHOT
option just means that the snapshot, once created, won't be exported for
use by other sessions.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-07-17 11:47:48 | Re: User documentation vs Official Docs |
Previous Message | Fabio Pardi | 2018-07-17 11:07:44 | Re: Query to monitor index bloat |