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

From Craig Ringer
Subject Re: Planning incompatibilities for Postgres 10.0
Date
Msg-id 51A3F329.4070709@2ndquadrant.com
Whole thread Raw
In response to Re: Planning incompatibilities for Postgres 10.0  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Planning incompatibilities for Postgres 10.0  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Planning incompatibilities for Postgres 10.0  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
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 can't think of any major syntax warts and grandfathered quirks that'd
be really great to get rid of if we had the freedom to break things.

-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: adding import in pl/python function
Next
From: Craig Ringer
Date:
Subject: Re: pgbench --startup option