jajool
Here are some of the main issues that I have encountered so far:
1. Queries on large tables (around 10 GB) are slow even when "index only scan" is used because of MVCC and the way postgreSQL manages concurrency.
2. Hot-standby instances can't be used for anything serious since all queries are dropped regularly (I believe it's not safe to use "hot_standby_feedback" config to overcome this issue).
3. It is not possible to have tables with heavy "update" workflows. (because of simultaneous autovaccum execution)
I would be very happy if anyone could show me that I am wrong.
Ask HN: What should we do if someone is crawling our website?
A couple days ago I found out someone was crawling our website. she was sending low traffic (150 rpm) and it was not a real problem! (we have around 15k rpm on average).I created an automated service to find crawler IPs and ban them, I did this for fun (parsing stream of requests, finding malicious behavior and blocking using firewall API was a challenging task).Not only this service didn't...
Ask HN: The Article About Swagger
recently an article about swagger made to the first page of HN. it was a complete guide about different types of swagger and its effect i can't find it anymore can someone send the link. thanks.
https://github.com/zichongkao/selectstarsql
here is the Github repository in case anyone wants to send PRs or start the project.
> For example, can you tell what the two functions below are doing? Probably you can tell for the first one, but unlikely for the second (or your name is Jaime Fernández del Río and you don't need to read this book).
there is one thing for sure nobody in iran wants a nuclear weapon.