Re: [HACKERS] Binary cursor header changed from 20 to 16 Bytes? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Binary cursor header changed from 20 to 16 Bytes?
Date
Msg-id 1818.933618160@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Binary cursor header changed from 20 to 16 Bytes?  ("G. Anthony Reina" <reina@nsi.edu>)
List pgsql-hackers
"G. Anthony Reina" <reina@nsi.edu> writes:
> The only thing that seems to have problems is when you select multiple
> variables. For this case, you have to put all of your arrays at the
> end.

That doesn't make a lot of sense to me either.  What happens if you
don't?

> I don't need to offset by 16 bytes to get the 2nd and 3rd column (cycles and
> time_instants); I only need to do this for the 1st column (repetition).

Right, there'd not be any array overhead for non-array datatypes...
        regards, tom lane


pgsql-hackers by date:

Previous
From: "G. Anthony Reina"
Date:
Subject: Re: [HACKERS] Binary cursor header changed from 20 to 16 Bytes?
Next
From: "G. Anthony Reina"
Date:
Subject: Re: [HACKERS] Binary cursor header changed from 20 to 16 Bytes?