PROTECTED]
Cc: pgsql-hackers@postgresql.org
Sent: Wednesday, April 18, 2007 6:38 PM
Subject: Re: [HACKERS] modifying the table function
Islam Hegazy [EMAIL PROTECTED] writes:
I wonder if I am on the right track or not and how to know such kind of
message sent from the server?
Seems like you're doing
from the server?
Regards
Islam Hegazy
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
To: Islam Hegazy [EMAIL PROTECTED]
Cc: pgsql-hackers@postgresql.org
Sent: Tuesday, April 17, 2007 1:44 AM
Subject: Re: [HACKERS] modifying the table function
Islam Hegazy [EMAIL PROTECTED
Islam Hegazy [EMAIL PROTECTED] writes:
I wonder if I am on the right track or not and how to know such kind of
message sent from the server?
Seems like you're doing it the hard way. Wouldn't it be easier to fix
the client to display data before it's received the whole query result?
Hi there
I made some changes in postgresql source code to let the table function work in
iteration fashion rather than materialization fashion. My main modifications
are in 'exec_simple_query' function, I changed 'portalRunSelect' to return just
one tuple instead of 'FETCH_ALL'. I made other
Islam Hegazy [EMAIL PROTECTED] writes:
My question is how to inform the client that there is a tuple to display =
and return back to the backend to continue the query execution?
I'd suggest you start by reading
http://developer.postgresql.org/pgdocs/postgres/protocol.html
and then develop a
Hi there
I am trying to modify the execution of the table function to work in iterator
fashion instead of materializing the output. I have been digging the Postgresql
code source for about a month now and I can figure out where the execution of
the table function works. I will be very grateful
