immudb
immudb copied to clipboard
update postgres wire protocol
TBD
I was going to file an issue regarding the PostgreSQL wire protocol regarding a denial of service vector. Running curl localhost:5432
results in the immudb
binary panicking and restarting.
Is there any point in filing an issue?
I was going to file an issue regarding the PostgreSQL wire protocol regarding a denial of service vector. Running
curl localhost:5432
results in theimmudb
binary panicking and restarting.Is there any point in filing an issue?
@grawlinson thanks for reporting the issue. Yes, feel free to open a new issue with the details about the crash, it makes sense to understand and fix the problem before we update the Postgres wire protocol.
I was going to file an issue regarding the PostgreSQL wire protocol regarding a denial of service vector. Running
curl localhost:5432
results in theimmudb
binary panicking and restarting. Is there any point in filing an issue?@grawlinson thanks for reporting the issue. Yes, feel free to open a new issue with the details about the crash, it makes sense to understand and fix the problem before we remove the Postgres wire protocol.
@zaza81 Does it mean that the Postgres protocol cannot be used in new versions in the future? If so, what are the alternatives? I think it is very competitive that immudb can provide relational database capabilities.
@letian0805 sorry, my bad. It's about updating postgres wire protocol, not removing.
Hi all, there are any news about this issue? Will the upgrade of postgres wire protocol be present in the next release? Currently, there is v9.6 and it is EOL as described here.