From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Mikko Tiihonen <mikko(dot)tiihonen(at)nitorcreations(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [JDBC] Optimize postgres protocol for fixed size arrays |
Date: | 2011-11-22 23:41:46 |
Message-ID: | CA+0W9LMJM-XjvDPcN7kQEp1O1UHtp1qoXV_n-P9nXCzZWKKg1w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On 23 November 2011 10:47, Mikko Tiihonen
<mikko(dot)tiihonen(at)nitorcreations(dot)com> wrote:
> Here is a patch that adds a new flag to the protocol that is set when all
> elements of the array are of same fixed size.
> When the bit is set the 4 byte length is only sent once and not for each
> element. Another restriction is that the flag
> can only be set when there are no NULLs in the array.
How does a client detect that this feature is supported?
At a glance the JDBC patch doesn't use it on the send path, but
presumably clients could use this when sending binary-format arrays to
the server - but only if the server understood the format.
(Ideally a pair of settings would be useful here - one to say "the
server understands the new format" and another the client sets to say
"please use the new format" that defaults to off - then you could
avoid confusing old clients, too)
Oliver
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-11-22 23:52:24 | Re: [JDBC] Optimize postgres protocol for fixed size arrays |
Previous Message | Simon Riggs | 2011-11-22 23:40:29 | Re: Not HOT enough |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-11-22 23:52:24 | Re: [JDBC] Optimize postgres protocol for fixed size arrays |
Previous Message | Merlin Moncure | 2011-11-22 22:46:24 | Re: Optimize postgres protocol for fixed size arrays |