-
Notifications
You must be signed in to change notification settings - Fork 590
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
SQL parameter error when querying risingwave via Postgres FDW #17661
Comments
Thanks for your feedback! Will take a look soon. |
This issue has been open for 60 days with no activity. If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the You can also confidently close this issue as not planned to keep our backlog clean. |
Ping @KeXiangWang |
🥵 Will take a look soon |
|
Thanks for your work! But I was wondering "Postgres sometimes will relay the extended parts to it's FDW engine", why "sometimes"? This is an undeterministic behavior? |
I'm not entirely sure about this, but it appears to be somewhat deterministic since it consistently sends an extended (parameterized) query on the 10th attempt. But in general, the |
Describe the bug
I build some tables in risingwave, and import them as foreign tables to postgres via FDW (postgres_fdw plugin), then I query postgres foreign tables using SpringData JPA (which uses Hibernate inside). I execute one same query for 10 times, for the first 9 times everything woks fine, but at the last time, risingwave throws error as shown in
Error messge/log
below.I inspected all this 10 times query SQL statement genereated by hibernate and I found they are same. I dumped risingwave's query log and I found that postgres_fdw deliver a wrong SQL to risingwave at the last time which is:
I show the detailes in
Error message/log
andTo Reproduce block
below.Error message/log
To Reproduce
Expected behavior
For the first 9 times, everything works fine, and you can see the correct SQL in RisingWave's query.log. And at the 10th time, query failed.
How did you deploy RisingWave?
via Docker Compose, one machine for all node, standalone mode. My docker-compose.yml is
The version of RisingWave
RisingWave version (
select version();
):PostgreSQL 13.14.0-RisingWave-1.9.2 (fbf1343627e9bc018930efb7f72f7fd19c15d2d0)
Postgres version (
select version();
):PostgreSQL 14.1 (Debian 14.1-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
SpringBoot version: 3.2.1,
SpringData JPA version: 3.2.1,
Spring version 6.1.2
Postgresql driver version: 42.6.0,
hibernate core version: 6.4.1
Additional context
@ke
The text was updated successfully, but these errors were encountered: