Recursive Parent-Child Function Bottom Up - Mailing list pgsql-general

From Avi Weinberg
Subject Recursive Parent-Child Function Bottom Up
Date
Msg-id DB9PR07MB718032F033C6D95B92E5BAAECBE89@DB9PR07MB7180.eurprd07.prod.outlook.com
Whole thread Raw
Responses Re: Recursive Parent-Child Function Bottom Up  (Rob Sargent <robjsargent@gmail.com>)
Re: Recursive Parent-Child Function Bottom Up  (Rob Sargent <robjsargent@gmail.com>)
Re: Recursive Parent-Child Function Bottom Up  (Alban Hertroys <haramrae@gmail.com>)
List pgsql-general

Hi,

 

I would like to populate the children_ids column with all the ids of the children recursively (+ grandchildren etc.)

If I do it top-bottom I will end up doing extra work since there is no need to go all levels down if I can just compute my IMMEDIATE children "children_ids" and just concatenate all their lists.

 

I looked at https://stackoverflow.com/questions/41376655/how-can-i-traverse-a-tree-bottom-up-to-calculate-a-weighted-average-of-node-va

But was not able to get it to work on my case.  

 

Your assistance is most welcome!

 

 

create table tree(id int primary key, parent int, children_ids text);

insert into tree (id, parent) values

(273,   0),

(274,      273),

(275,      273),

(277,      273),

(278,      277),

(280,      275),

(281,      280),

(282,      281),

(283,      282),

(284,      282),

(285,      282),

(286,      282),

(287,      282),

(288,      282),

(289,      282),

(290,      281),

(291,      290),

(292,      290),

(293,      290),

(294,      290),

(295,      290);

IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you should not copy or use this e-mail for any purpose nor disclose its contents to any person.

pgsql-general by date:

Previous
From: Rama Krishnan
Date:
Subject: Logical replication from Rds into on-premise
Next
From: Marcin Barczynski
Date:
Subject: Re: Why does VACUUM FULL pg_class sometimes wait for ShareLock on another transaction after getting AccessExclusiveLock on pg_class?