Add “schema change notifications”.
Currently “-ng” uses a bit of magic, mid query, to detect when schema changes have occurred. This is how the binary
typesremain correctly mapped. A notification sent whenever a type (basically anything in pg_type) is altered in any
waywould solve this problem perfectly. It would be best if the notification included the type oids that changed.
The infrastructure is already there in both needed respects, notifications & it already knows internally about the
changes)so this should be something that could be easily added to the current protocol.
> On Dec 29, 2015, at 12:07 PM, Vladimir Sitnikov <sitnikov.vladimir@gmail.com> wrote:
>
> Hi,
>
> I've collected "wanted features" page (see [1], [2]).
> A dedicated file in pgjdbc seems fine for me. If you know better
> location, waive a hand.
>
> If you remember more, or if you want your name with "+1" to appear
> there, comment on the PR or file a PR as that one is merged in.
>
> [1]: https://github.com/pgjdbc/pgjdbc/pull/478
> [2]: https://github.com/pgjdbc/pgjdbc/blob/protocol_wanted_features/backend_protocol_v4_wanted_features.md
>
> PS. As always, it would be nice if you proofread the file as I am
> having troubles with mastering English.
>
> Vladimir
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
