From: | Álvaro Hernández Tortosa <aht(at)8Kdata(dot)com> |
---|---|
To: | Kevin Wooten <kdubb(at)me(dot)com>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Backend protocol wanted features |
Date: | 2016-01-02 20:55:28 |
Message-ID: | 56883940.2090100@8Kdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 29/12/15 20:22, Kevin Wooten wrote:
> Add “schema change notifications”.
This is an interesting idea.
I wonder, however, if a protocol message is the place for it. I
think it belongs to logical decoding (and yes, I know there is no
current support for DDL in logical decoding, but there should be). So I
wouldn't add this specifically to the febe protocol.
On another topic, I'd look into considering some of the ideas of
the "protocol" designed by the pglogical_output plugin
(http://www.postgresql.org/message-id/CAMsr+YGc6AYKjsCj0Zfz=X4Aczonq1SfQx9C=hUYUN4j2pKwHA@mail.gmail.com)
for possible inclusion as first-class constructs in a new version of the
protocol.
Álvaro
--
Álvaro Hernández Tortosa
-----------
8Kdata
>
> Currently “-ng” uses a bit of magic, mid query, to detect when schema changes have occurred. This is how the binary types remain correctly mapped. A notification sent whenever a type (basically anything in pg_type) is altered in any way would 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(dot)vladimir(at)gmail(dot)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(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-jdbc
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2016-01-04 17:26:16 | Re: Backend protocol wanted features |
Previous Message | Markus KARG | 2015-12-31 14:10:45 | Re: Recent backward compatibility break in PreparedStatement.setObject() |