Message-ID: <gh-pgjdbc-pgjdbc-3049-c1836021743@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 01 Dec 2023 12:13:52 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3049: TypeInfoCache should be clearable/resetable
In-Reply-To: <gh-pgjdbc-pgjdbc-3049@github.com>
References: <gh-pgjdbc-pgjdbc-3049@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 1836021743
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3049
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3049#issuecomment-1836021743
Content-Type: text/plain; charset=utf-8

I have not looked into this exact case, however, here's a way re-executing might be implemented: https://github.com/pgjdbc/pgjdbc/pull/451/files#diff-fb626514a44e1fd93551464de0ba369def2b0513a7232ce12d9c3040ea98d211R336

We could probably monitor "drop type" queries, and invalidate the relevant caches automatically. Sure it won't heal all the cases, but it might resolve many issues automatically.