Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is a missing feature(notify-listen) about pg databases. #33296

Open
zzyReal666 opened this issue Oct 18, 2024 · 0 comments
Open

There is a missing feature(notify-listen) about pg databases. #33296

zzyReal666 opened this issue Oct 18, 2024 · 0 comments

Comments

@zzyReal666
Copy link
Contributor

zzyReal666 commented Oct 18, 2024

Bug Report

For English only, other languages will not accept.

Which version of ShardingSphere did you use?

5.5.1

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

proxy

Expected behavior

There is 2 psql client named listener and notifier.
step 1: listener listen an issue
image
step 2: notifier send message to issue
image
step 3: listener execute any sql such as 'select 1;',will get the message from notifier
image

Actual behavior

The proxy parsed the sql correctly, but there was no reaction;
image

Reason analyze (If you can)

Maybe the proxy does not transparently transmit these network packets.

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

  1. psql -h <host_ip> -p -U -d <database_name> to login database;
  2. listener : listen [any String such as test]
  3. notifier: notify [test],'hello world'
  4. listener : any sql,such as 'select 1;'

Perhaps other databases support similar mechanisms

Example codes for reproduce this issue (such as a github link).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants