Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #5681: Using set returning function as subrequest can result losing rows in result set - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5681: Using set returning function as subrequest can result losing rows in result set
Date
Msg-id 28500.1285706181@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5681: Using set returning function as subrequest can result losing rows in result set  ("Maksym Boguk" <Maxim.Boguk@gmail.com>)
List pgsql-bugs
Tree view 
"Maksym Boguk" <Maxim.Boguk@gmail.com> writes:
> Oops... two rows where function returned zero rows just disappeared.

Yup, that's expected.  This is one of many reasons why set-returning
functions in the targetlist aren't an especially good idea.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Maksym Boguk"
Date:
Subject: BUG #5681: Using set returning function as subrequest can result losing rows in result set
Next
From: Tom Lane
Date:
Subject: Re: BUG #5680: Failure to start: too many private dirs demanded