some hints to understand the plsql cursor.

From: Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: some hints to understand the plsql cursor.
Date: 2019-02-27 11:11:54
Message-ID: CAKU4AWqoGO=Lj8gpoA_VvW3r2HfFUGTs4oaEnW_yYp7xw=gbgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

actually I'm hacking pg for a function like :
1. define a select query.
2. client ask for some data. and server reply some data. server will do
NOTHING if client doesn't ask any more..
3. client ask some data more data with a batch and SERVER reply some data
then. then do NOTHING.

currently the simple "select * from t", the server will try to send the
data to client at one time which is not something I want.

by looking into the plsql, looks it has some api like:

fetch 10 from cursor_1;
fetch 10 from cursor_1;

I'm lacking of the experience to hack plsql. so my question are:
1. Does pg has some codes which act like the "ask -> reply -> ask again
-> reply again" on the server code? currently I'm not sure if the above
"fetch" really work like this.
2. any resources or hint or suggestion to understand the "fetch"
statement?

Thanks

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-02-27 12:32:17 Re: Segfault when restoring -Fd dump on current HEAD
Previous Message Andy Fan 2019-02-27 10:59:13 Re: When is the MessageContext released?