Re: Backend protocol wanted features

On 2 January 2016 at 15:55, Álvaro Hernández Tortosa <aht@8kdata.com> wrote:

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

Putting this into logical decoding doesn't really help us as that would require the driver to connect to the logical decoding stream as well.  

While I understand it is required for LD. The driver needs it for a different reason.

    I agree. Somehow :)

    I mean: I understand the driver needs this information. 100% agreed there. But adding new protocol messages that "duplicate" the functionality that should belong (IMHO) only to LD, doesn't make sense. Sure, it is a poor fit a LD client for a JDBC driver. But I still think it's the way to go. That was the main starting point for us thinking about Phoebe, you know :)

    So rather than asking everybody to add new messages to the protocol to support this, wouldn't it be better to support LD in the driver?

    Cheers,

    Álvaro

-- 
Álvaro Hernández Tortosa


-----------
8Kdata

Dave Cramer

davec@postgresintl.com

www.postgresintl.com

--
Á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.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

--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc