| From: | Tom Dunstan <tom(at)tomd(dot)cc> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Reading and writing off-heap data |
| Date: | 2017-09-25 10:47:05 |
| Message-ID: | CAPPfruyp3Zt99+vWpmqawuFOCCQx_3Zi3cKMqeZyXOWqxF1DZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Hi Vladimir!
On 25 September 2017 at 17:50, Vladimir Sitnikov <
sitnikov(dot)vladimir(at)gmail(dot)com> wrote:
>
>
> That is of no question. The question is "do you intend to call
user-provided code right from
org.postgresql.core.v3.QueryExecutorImpl#processResults, case 'D': // Data
Transfer (ongoing Execute response)" ?
We'd have to call it inside PGStream#receiveTupleV3 I think, as that's
where the byte arrays for each field are being allocated. Or potentially it
could be moved into the tuple class itself.
As with PR 953 https://github.com/pgjdbc/pgjdbc/pull/953 we'd call the
user-provided code on a guarded InputStream so that we know they can't mess
the stream up.
Cheers
Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Dunstan | 2017-09-25 10:48:02 | Re: Reading and writing off-heap data |
| Previous Message | Vladimir Sitnikov | 2017-09-25 08:20:16 | Re: Reading and writing off-heap data |