I have seen many PostgreSQL benchmarks having solid performance with TB data but my real world experience is the complete opposite.
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.
thanks a lot. it's an awesome project. in the introduction it was stated that this project is using Github pages for hosting but i couldn't find the repository address anywhere.
this book is amazing! specially the authors sense of humor makes reading it fun.
> 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).
majority of young people are happy! to tell you the troth sanctions were a real pain for us, imagine every time i use internet and i forget to connect VPN i get the "Unavailable in your country message" while visiting Unity or Google Code websites.
but on the other hand there are some who are not that happy they think with this agreement we have lost decades of effort toward peacefull nuclear energy.
there is one thing for sure nobody in iran wants a nuclear weapon.