Should I use ltree in postgresql? And what is the best way to manually organize a tree structure?

Question

PostgreSQL

Has anyone used the ltree add-on in postgresql, is it convenient and does it affect performance? And how is it better to organize a structure where there can be only one parent, several children, but each child of the parent must be unique among its own?
For example, from these 4 methods:
Adjacency List (“adjacency list”)
Materialized Path (“materialized path”)
Nested Sets (“nested sets”)
Closure Table (“link table”)

Answer 1

Yes, use ltree for postgres: convenient, efficient