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

Re: Hot Standby and handling max_standby_delay

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hot Standby and handling max_standby_delay
Date: 2010-01-16 20:12:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sat, 2010-01-16 at 18:20 +0000, Simon Riggs wrote:
> On Sat, 2010-01-16 at 11:37 -0500, Tom Lane wrote:
> > Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > > I'm wondering if it wouldn't just be easier to put in a plugin for
> > > recovery conflict handling, so the user can decide what to do
> > > themselves. That seems like a better plan than chewing through these
> > > issues now. 
> > 
> > Making it a plugin doesn't solve anything.  This is not the kind of
> > thing where people can come up with some random policy and it will
> > work well.  Anyone competent to invent a better policy would be quite
> > capable of modifying the source to suit themselves.
> Agreed, with some regrets.

Although I agree in principle, I have to say that a plugin might make
sense. Yes... the person is good enough to modify the code, but should
they? A plugin allows them to make those decisions without running a
custom code base for core. 

Just a thought.

Joshua D. Drake

> -- 
>  Simon Riggs 

-- Major Contributor
Command Prompt, Inc: - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.

In response to

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2010-01-16 20:44:26
Subject: Re: Review: Patch: Allow substring/replace() to get/set bit values
Previous:From: Erik RijkersDate: 2010-01-16 18:54:33
Subject: Re: review: More frame options in window functions

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