Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-6099

ResultSet not being closed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Minor Minor
    • None
    • None
    • postgresql-connector
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Low

      What Debezium connector do you use and what version?

      Debezium Connector For PostgreSQL » 2.1.2.Final

      What is the connector configuration?

      Not relevant outside using Avro maybe.

      What is the captured database version and mode of depoyment?

      (not relevant)

      What behaviour do you expect?

      ResultSet is closed, so pids are finalized in PostgreSQL

      What behaviour do you see?

      Pids are held in PostgreSQL for queries like:

       

      SELECT relreplident FROM pg_catalog.pg_class c LEFT JOIN pg_catalog.pg_namespace n ON c.relnamespace=n.oid WHERE n.nspname=$1 and c.relname=$2

       

      The pids are in:

      | wait_event_type | wait_event | state               |
      | Client          | ClientRead | idle in transaction |

      This is because the ResultSet is not closed in https://github.com/debezium/debezium/blob/5a063867df699225cc08dc1998e6530af2996510/debezium-connector-postgres/src/main/java/io/debezium/connector/postgresql/connection/PostgresConnection.java#L176-L178

      Do you see the same behaviour using the latest relesead Debezium version?

      yes

      Do you have the connector logs, ideally from start till finish?

      (not relevant)

      How to reproduce the issue using our tutorial deployment?

      Would be easy to do.

       

              Unassigned Unassigned
              enzo.cappa Enzo Cappa (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: