Re: pg_stop_backup does not complete

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: jd(at)commandprompt(dot)com
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stop_backup does not complete
Date: 2010-02-24 19:02:30
Message-ID: 1267038150.3752.6651.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2010-02-24 at 10:17 -0800, Joshua D. Drake wrote:

> Basically the reports boil down to people who are actually going to be
> dealing with this in the field. Simon with respect you have been 6 feet
> deep in code for too long on this. You need to step back and take some
> constructive feedback from those that are dealing with the production
> issues and do so with a smile.

I receive constructive feedback all the time from the many users I deal
personally and directly with each week.

You make the mistake of assuming that someone that can develop has no
solution experience. That is exactly how I fund further development, so
you are off base by a long way.

The way this works currently is based on production feedback. This post
is about non-production usage. Until someone comes up with a truly
constructive suggestion that takes account of the issues that cause the
current design, it won't get traction with me.

--
Simon Riggs www.2ndQuadrant.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-02-24 19:03:07 Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf option to a new chapter.
Previous Message Simon Riggs 2010-02-24 18:53:56 Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf option to a new chapter.