4 ms·
> Also typical database uses 96% of the time for logging, locking etc. and 4% percent for actual data operations That's a strange claim, in my work it's always
by throwaway_pdp09 6y ago
> Also typical database uses 96% of the time for logging, locking etc. and 4% percent for actual data operations
That's a strange claim, in my work it's always been 100% data ops.
> “Letting people connect directly to the database is a madness” — yes it is.
why?
> Killing database by multiple connections from single network port is simply impossible in real life scenario. You will long run out of free ports
Depends entirely on the workload. And it's very possible. All too entirely so.
- taffer 6y ago> why? while true: select count(*) from huge_table thats why.
- somurzakov 6y ago1.if that table is a materialized view with columnstore index then you can run it as many times as you want. 2. always hide postgREST behind API gateway/load balancer/waf/ids+ips/rate limiter and you will be more secure from stuff lile this
- ruslan_talpa 6y agoYou can setup a view (accessed by postgrest) that returns an error when there are no (correct) filters in the query so that takes care of select *... problem (also you can have the same logic in the proxy (nginx) layer