Re: Dividing progress/debug information in pg_standby, and stat before copy - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Dividing progress/debug information in pg_standby, and stat before copy
Date
Msg-id 9837222c1001260141p1115c678n2eb691f631d2ee3e@mail.gmail.com
Whole thread Raw
In response to Re: Dividing progress/debug information in pg_standby, and stat before copy  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Dividing progress/debug information in pg_standby, and stat before copy  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
2010/1/26 Tom Lane <tgl@sss.pgh.pa.us>:
> Greg Smith <greg@2ndquadrant.com> writes:
>> [ Greg and Selena discuss filing some rough edges off pg_standby ]
>
> Maybe I'm missing something, but I thought pg_standby would be mostly
> dead once SR hits the streets.  Is it worth spending lots of time on?
>
> The ideas all sound good, I'm just wondering if it's useful effort
> at this point.

I think there are definite use-cases for pg_standby as well, even when
we have SR. SR requires you to have a reasonably reliable network
connection that lets you do an arbitrary TCP connection. There are a
lot of scenarios that could still use the
"here's-a-file-you-choose-how-to-get-it-over-to-the-other-end" style
transfer, and that don't necessarily care that there is a longer
delay.

*Most* people will still use SR, I'm sure.


-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy
Next
From: Boszormenyi Zoltan
Date:
Subject: Re: ECPG patch 4.1, out-of-scope cursor support in native mode