Re: Planning incompatibilities for Postgres 10.0

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Planning incompatibilities for Postgres 10.0
Date: 2013-05-28 00:21:16
Message-ID: 51A3F87C.6070304@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Flower 2013-05-28 01:39:59 Re: Planning incompatibilities for Postgres 10.0
Previous Message Craig Ringer 2013-05-28 00:20:20 Re: high io BUT huge amount of free memory