current community

your communities

more stack exchange communities

Stack Exchange
tour help
careers 2.0
Take the 2-minute tour ×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
up vote 0 down vote favorite

I am a newbie in PostgreSQL (using v9.0) and wanted to know if using return next and Return query in the same function is possible without exiting the function before attaching the results in the resultset?

CREATE TYPE return_type AS
   (paramname character varying,
    value character varying);

CREATE OR REPLACE FUNCTION myfuntion(param1 character varying)
RETURNS SETOF return_type AS
declare
r return_type;
message varchar;
status integer;
$BODY$
BEGIN
o_call_status := 0;
o_call_message := '';
        Return query Select 'mystatus' as paramName, status::varchar as value;
        Return query Select 'mymessage' as paramName, message as value;

       for r in SELECT 'mycolumnname1' as paramName,mycolumn1 as value FROM tb1 
                WHERE column1 = val
                UNION ALL
                SELECT 'mycolumnname2' as paramName,mycolumn2 as value  FROM tb1 
                WHERE column1 = val
                UNION ALL
                SELECT 'mycolumnname3' as paramName,mycolumn3 as value  FROM tb2 
                WHERE column1 = val1 AND
                column4 = val4  loop
          return next r;
        end loop;

        END;
        $BODY$
LANGUAGE plpgsql VOLATILE
share|improve this question

2 Answers 2

up vote 1 down vote accepted

Returning from a plpgsql function

You can mix RETURN NEXT and RETURN QUERY freely and repeatedly. The underlying principle is that plpgsql builds the table locally and does not return until the function is finished:

Per documentation:

Note: The current implementation of RETURN NEXT and RETURN QUERY stores the entire result set before returning from the function, as discussed above.

That means you can even raise en exception to abort the operation if you are unsatisfied with the results so far and the client won't see a thing. We also included an example in the manual demonstrating this, just above said quote.

Cross tabulation

As for what you are trying do achieve, consider the crosstab() function fro the tablefunc extension. Related answer with ample details:
PostgreSQL Crosstab Query

share|improve this answer
    
Thanks @Erwin, that web page in the documentation was exactly the explanation I needed to understand when to use those keywords. So the answer is only when used the return keyword like this return; will cause the termination of the function. –  Douglas Apr 24 at 18:35
    
@Douglas: Yes. And when the function reaches the end without explicit RETURN, the answer (if any) is sent as well. Works with OUT parameters, too. Only the basic form declared with RETURNS *type* requires an explicit RETURN *value*;. –  Erwin Brandstetter Apr 24 at 20:52
up vote 0 down vote

I'm unsure if you can mix the two (try it…).

That said, it'll be much more efficient in you use-case to write a single query with a union all clauses that returns all rows directly:

return query
select 'mystatus' as paramName, status::varchar as value
union all
select 'mymessage' as paramName, message as value
union all
SELECT 'mycolumnname1' as paramName,mycolumn1 as value
FROM tb1
WHERE column1 = val
union all
…

You might also find this contrib module helpful, btw:

http://www.postgresql.org/docs/current/static/tablefunc.html

And, if possible, revisit your schema or the way you use it, so you don't need this kind of function to begin with — set returning functions that return potentially large sets can be particularly inefficient. In your case, it seems like you want three columns. Why not simple use?

select col1, col2, col3 from tbl
share|improve this answer
    
Hi @Denis, I am testing Postgres for a possible migration for one of ours products, so changing that kind of things is not possible. Status and message are variables inside the same function but obtained in different situations so can not be used in the same query. That being said, how can I attach different queries results with same field types in a same function resultset. Can be used return query or other keyword multiple times for that? –  Douglas Apr 23 at 21:02
    
Methinks try it as you wrote it, and if PG complains about mixing return next and return query, or multiple return query, use return next all over. Return query is faster insofar as I can recollect, btw, so if you can change that last one to use return query instead of return next, it's good too. –  Denis Apr 23 at 21:08

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.