-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Table Busy is often displayed when data is inserting #1461
Comments
QuestDB does not support concurrent writes to the same table from Postgres wire protocol at the moment. REST api automatically retries inserts and ILP allow writing from concurrent connections |
Wow, that is a big gotcha. I burned too many hours messing around with the configuration in hopes of getting past this. Thx @ideoma for explaining. Is there anywhere were I can find other similar limitations or know if this is on their radar? |
Just ran into this today after a ton of work setting up our logging with Postgres. This is a huge handicap for Postgres in my opinion and it doesn't seem to be actually documented anywhere. Is there a timeline on when or if this might be fixed? |
Should be fixed now on WAL-enabled tables: https://questdb.io/docs/concept/write-ahead-log/ |
已收到,会尽快查看,谢谢!(自动回复)
|
The error message is:
The text was updated successfully, but these errors were encountered: