title: Postgres table with thousands of partition
body: <p>I have a postgres table (in postgres12) which is supposed to have thousands of partitions (200k at least) in near future.</p>
  <p>Here is how I am creating the parent table:</p>
  <pre><code>create table if not exists content (
      key varchar(20) not NULL,
      value json not null default '[]'::json
  ) PARTITION BY LIST(key)
  </code></pre>
  <p>And then adding any given child tables like:</p>
  <pre><code>create table if not exists content_123 PARTITION OF content for VALUES in ('123');
  </code></pre>
  <p>Also I am adding an index on top of the child table for quick access (since I will be accessing the child table directly):</p>
  <pre><code>create index if not exists content_123_idx on content_123 using btree(key) 
  </code></pre>
  <p>Here is my question: I have never in the past managed this many partitions in a postgres table so I am just wondering is there any downside of doing what I am doing? Also, (as mentioned above) I will not be querying from the parent table directly, but will read directly from individual child tables.</p>