| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Tom Dunstan <pgsql(at)tomd(dot)cc>, Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Reading and writing off-heap data |
| Date: | 2017-09-25 08:20:16 |
| Message-ID: | CAB=Je-F8gQ6QRVHvrDFnKutWWKPT3BNxPOwpvvdqTod4iFMiHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Tom>I'll try to quantify it though. Do we have any existing test for these
sorts of things? If not I'll just generate a bunch of data and pull it
through - seems easy enough.
>Code affecting where incoming data goes would have to be registered with
the statement object or similar before execution.
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)" ?
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Dunstan | 2017-09-25 10:47:05 | Re: Reading and writing off-heap data |
| Previous Message | Vladimir Sitnikov | 2017-09-25 08:13:07 | Re: Timestamp parameter gets sent as date |