From: | Emrul <emrul(at)emrul(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Dynamic execution returning large result sets |
Date: | 2016-11-07 01:12:54 |
Message-ID: | 1478481174567-5929177.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I have a function that returns an SQL string as follows:
CREATE OR REPLACE FUNCTION t1() RETURNS text AS
$$
BEGIN
RETURN 'SELECT * FROM mytable';
END
$$ LANGUAGE plpgsql;
and I want to create a second function (t2) that will execute the string
returned by t1() and return the results. I thought about using RETURN QUERY
EXECUTE as documented here:
https://www.postgresql.org/docs/9.6/static/plpgsql-control-structures.html
but there's a note towards the end that says '/if a PL/pgSQL function
produces a very large result set, performance might be poor: data will be
written to disk to avoid memory exhaustion, but the function itself will not
return until the entire result set has been generated./'
Is there any other way I can achieve execution of the dynamic SQL from t1()
without having the whole result set retrieved inside the function itself?
note: My example above is simplified, my real t1() function takes some
parameters and generates SQL depending upon those parameters.
Thanks!
--
View this message in context: http://postgresql.nabble.com/Dynamic-execution-returning-large-result-sets-tp5929177.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-11-07 01:18:52 | Re: Dynamic execution returning large result sets |
Previous Message | Guillaume Lelarge | 2016-11-06 20:33:20 | Re: Exclude pg_largeobject form pg_dump |