Re: PLJava and Database Meta Data - Mailing list pgsql-jdbc

From Thomas Hallgren
Subject Re: PLJava and Database Meta Data
Date
Msg-id thhal-0aEnoAuNMxicXo3uf6+PCZQjtO2fifP@mailblocks.com
Whole thread Raw
In response to Re: PLJava and Database Meta Data  (Markus Schaber <schabios@logi-track.com>)
List pgsql-jdbc
Markus Schaber wrote:

>Okay, so this is fine for primitive types. How does SPI deal with
>complex types?
>
>
A complex type is represented by a C-structure called HeapTuple. A
HeapTuple is associated with a TupleDesc that acts as its description.
The HeapTuple is passed by reference (a C-language pointer) and PLJava
will obtains its individual values as Datums using a function called
SPI_getbinval. An individual value may of course be a reference to
another complex type.

Complex types are created using the function heap_form_tuple.

>Yes, I have. Especially for large geometries. In our database, we have
>geometry objects up to 20MB per piece. Also, in PostGIS, send/receive
>binary representation differs slightly from internal representation (and
>input/output text is even more overhead).
>
>
Ok. We are probably talking about different things. I'm referring to the
internal C-functions that are executed directly in the backend.

- thomas



pgsql-jdbc by date:

Previous
From: Markus Schaber
Date:
Subject: Re: PLJava and Database Meta Data
Next
From: Markus Schaber
Date:
Subject: Re: PLJava and Database Meta Data