We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
net._http_response
This will be fixed on #68. Opening the issue to make the bug clear.
When having
postgres=# select count(*) from net._http_response; -[ RECORD 1 ] count | 50001 postgres=# select count(*) from net.http_request_queue; -[ RECORD 1 ] count | 0
Usage stays mostly at 2.6%CPU. Also notice the 6.7% MEM, which indicates there's a memory leak.
This is due to this DELETE:
pg_net/src/worker.c
Lines 442 to 445 in 70ea4cd
clock_timestamp() generates a full table scan each time it runs.
clock_timestamp()
The text was updated successfully, but these errors were encountered:
fix supabase#70, use limited delete for ttl
cae7a57
also use now() instead of clock_timestamp
f1cb851
8b8f53f
0f487bf
No branches or pull requests
This will be fixed on #68. Opening the issue to make the bug clear.
When having
Usage stays mostly at 2.6%CPU. Also notice the 6.7% MEM, which indicates there's a memory leak.
This is due to this DELETE:
pg_net/src/worker.c
Lines 442 to 445 in 70ea4cd
clock_timestamp()
generates a full table scan each time it runs.The text was updated successfully, but these errors were encountered: