I need to store about 600 million rows of property addresses across multiple counties. I need to have partitioning setup on the table as there will be updates and inserts performed to the table frequently and I want the queries to have good performance.
>From what I understand hash partitioning would not be the right approach in this case, since for each query PostgreSQL has to check the indexes of all partitions? Would list partitioning be suitable? if I want PostgreSQL to know which partition the row is it can directly load the relevant index without having to check other partitions. Should I be including the partition key in the where clause? I'd like to hear some recommendations on the best way to approach this. I'm using PostgreSQL 12
