Skip site navigation (1) Skip section navigation (2)

Re: Hot Standby query cancellation and Streaming Replication integration

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot Standby query cancellation and Streaming Replication integration
Date: 2010-02-28 22:15:18
Message-ID: 1267395318.20134.3178.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, 2010-02-26 at 03:33 -0500, Greg Smith wrote:

> I really hope this discussion can say focused on if and how it's 
> possible to improve this area, with the goal being to deliver a product 
> everyone can be proud of with the full feature set that makes this next 
> release a killer one. The features that have managed to all get into 
> this release already are fantastic, everyone who contributed should be 
> proud of that progress, and it's encouraging that the alpha4 date was 
> nailed.  It would be easy to descend into finger-pointing for why 
> exactly this particular problem is only getting more visibility now, or 
> into schedule-oriented commentary suggesting it must be ignored because 
> it's too late to do anything about it.  I hope everyone appreciates 
> wandering that way will not help make PostgreSQL 9.0 a better release.  
> This issue is so easy to encounter, and looks so bad when it happens, 
> that I feel it could easily lead to an embarrassing situation for the 
> community if something isn't done about it before release.

Thanks Greg. It's a great relief for me to hear someone else say this
and to watch a discussion about this important issue unfold.

-- 
 Simon Riggs           www.2ndQuadrant.com


In response to

pgsql-hackers by date

Next:From: Josh BerkusDate: 2010-02-28 22:38:28
Subject: Re: Re: Hot Standby query cancellation and Streaming Replication integration
Previous:From: Simon RiggsDate: 2010-02-28 21:58:51
Subject: Re: Hot Standby query cancellation and Streaming Replication integration

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group