| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Strange RETURN NEXT behaviour in Postgres 8.0 |
| Date: | 2005-02-16 20:32:47 |
| Message-ID: | 27975.1108585967@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Sergey E. Koposov" <math(at)sai(dot)msu(dot)ru> writes:
> Concerning to the exact form of my functions (using cursors, but still
> collecting all the data in the memory). As I understand this is the only one
> way (or just the simplest way ???)
> to execute fully dynamic queries returned by C function in PL/SQL.
> For the real functions which I use, instead of
> query = ''SELECT * FROM usno'';
> I have
> query = my_C_function(some_args);
Oh? I'd make a small side bet that the underlying error is in your C
function --- possibly it's tromping on some data structure and the
damage doesn't have an effect till later. If you can demonstrate the
problem without using any custom C functions then I'd be interested to
see a test case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | elein | 2005-02-16 20:43:59 | Re: Work on Table Inheritance |
| Previous Message | Sergey E. Koposov | 2005-02-16 20:28:45 | Re: Strange RETURN NEXT behaviour in Postgres 8.0 |