On Mon, Jun 26, 2023 at 8:50 AM Devin Ivy wrote:
> Any thoughts on why this may be, or where to go next to continue tracking
> this down? Also, could the primary key column order `(id, ancestor_id)` vs
> `(ancestor_id, id)` significantly affect the index size depending on the
> column cardinal
Hi all,
I have a suspiciously large index, and I could use a hand finding a root
cause for its size. This index supports the primary key for a closure
table that models threaded comments with columns `(id, ancestor_id,
depth)`. The primary key is composite: `(id, ancestor_id)`. The id
columns ar
