Re: Planning incompatibilities for Postgres 10.0 - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Planning incompatibilities for Postgres 10.0
Date
Msg-id 51A3F87C.6070304@commandprompt.com
Whole thread Raw
In response to Re: Planning incompatibilities for Postgres 10.0  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Planning incompatibilities for Postgres 10.0
List pgsql-hackers
On 05/27/2013 04:58 PM, Craig Ringer wrote:
>
> On 05/28/2013 12:41 AM, Simon Riggs wrote:
>> I'm happy with that.
>>
>> I was also thinking about collecting changes not related just to disk
>> format, if any exist.
> Any wire protocol or syntax changes?
>
> I can't seem to find a "things we want to do in wire protocol v4" doc in
> the wiki but I know I've seen occasional discussion of things that can't
> be done without protocol changes. Anyone with a better memory than me
> able to pitch in?
>
> What'd be required to support in-band query cancellation? Sending
> per-statement GUCs (to allow true statement timeout)?
>

I would like to see the ability to define if a query is read only at the 
protocol level, so that load balances that speak libpq can know what to 
do with the query without parsing it.

JD

-- 
Command Prompt, Inc. - http://www.commandprompt.com/  509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms   a rose in the deeps of my heart. - W.B. Yeats



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: high io BUT huge amount of free memory
Next
From: Gavin Flower
Date:
Subject: Re: Planning incompatibilities for Postgres 10.0