| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: tablecmds: clarify recurse vs recusing |
| Date: | 2026-01-19 16:21:42 |
| Message-ID: | 1080161.1768839702@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> writes:
> ... but I
> can't remember what could recurse = false, recursing = true mean.
It'd mean that we are operating on a child table but should not
recurse to its children (if any). Not sure if the case actually
arises, although it could make sense if we flattened the inheritance
tree into a list of target tables earlier on, which does happen in
many cases. But most of the code paths that do it that way don't
bother with recurse/recursing parameters.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2026-01-19 16:29:25 | Race conditions in logical decoding |
| Previous Message | Tom Lane | 2026-01-19 16:14:40 | Re: tablecmds: clarify recurse vs recusing |