[HACKERS] Query fails when SRFs are part of FROM clause (Commit id: 69f4b9c85f)
От | Rushabh Lathia |
---|---|
Тема | [HACKERS] Query fails when SRFs are part of FROM clause (Commit id: 69f4b9c85f) |
Дата | |
Msg-id | CAGPqQf3joLrjmR2FmQzYURb-_TxhW78tXhgYm+C66wXNjWH9ww@mail.gmail.com обсуждение исходный текст |
Ответы |
Re: [HACKERS] Query fails when SRFs are part of FROM clause (Commitid: 69f4b9c85f)
Re: [HACKERS] Query fails when SRFs are part of FROM clause (Commitid: 69f4b9c85f) |
Список | pgsql-hackers |
Consider the below test;
CREATE TABLE tab ( a int primary key);
SELECT *
FROM pg_constraint pc,
CAST(CASE WHEN pc.contype IN ('f','u','p') THEN generate_series(1, array_upper(pc.conkey, 1)) ELSE NULL END AS int) AS position;
Above query is failing with "set-valued function called in context that cannot
accept a set". But if I remove the CASE from the query then it working just good.
Like:
SELECT *
FROM pg_constraint pc,
CAST(generate_series(1, array_upper(pc.conkey, 1)) AS int) AS position;
This started failing with 69f4b9c85f168ae006929eec44fc44d569e846b9. It seems
check_srf_call_placement() sets the hasTargetSRFs flag and but when the SRFs
at the rtable ofcourse this flag doesn't get set. It seems like missing something
their, but I might be completely wrong as not quire aware of this area.
Rushabh Lathia
В списке pgsql-hackers по дате отправления: