diff options
author | Bruce Momjian <bruce@momjian.us> | 2002-10-03 17:11:12 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2002-10-03 17:11:12 +0000 |
commit | 620dddf88a46310abf741b6f13f388e0f809ea27 (patch) | |
tree | ced6c654d563c3c32e607d95a73cbc65d1f4ff3b /src/backend/executor/functions.c | |
parent | a0bf2503ea0d9a1a2208dd3cf74727bcda7e69d2 (diff) | |
download | postgresql-620dddf88a46310abf741b6f13f388e0f809ea27.tar.gz postgresql-620dddf88a46310abf741b6f13f388e0f809ea27.zip |
> The previous patch fixed an infinite recursion bug in
> contrib/tablefunc/tablefunc.c:connectby. But, other unmanageable error
> seems to occur even if a table has commonplace tree data(see below).
>
> I would think the patch, ancestor check, should be
>
> if (strstr(branch_delim || branchstr->data || branch_delim,
> branch_delim || current_key || branch_delim))
>
> This is my image, not a real code. However, if branchstr->data includes
> branch_delim, my image will not be perfect.
Good point. Thank you Masaru for the suggested fix.
Attached is a patch to fix the bug found by Masaru. His example now
produces:
regression=# SELECT * FROM connectby('connectby_tree', 'keyid',
'parent_keyid', '11', 0, '-') AS t(keyid int, parent_keyid int, level
int,
branch text);
keyid | parent_keyid | level | branch
-------+--------------+-------+----------
11 | | 0 | 11
10 | 11 | 1 | 11-10
111 | 11 | 1 | 11-111
1 | 111 | 2 | 11-111-1
(4 rows)
While making the patch I also realized that the "no show branch" form of
the function was not going to work very well for recursion detection.
Therefore there is now a default branch delimiter ('~') that is used
internally, for that case, to enable recursion detection to work. If
you need a different delimiter for your specific data, you will have to
use the "show branch" form of the function.
Joe Conway
Diffstat (limited to 'src/backend/executor/functions.c')
0 files changed, 0 insertions, 0 deletions