[Pgpool-hackers] [Pgpool-general] pgpool limitations

[Gurjeet Singh]

On Fri, Jul 29, 2011 at 7:38 PM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> > On Thu, Jul 28, 2011 at 10:40 PM, Tatsuo Ishii <ishii at sraoss.co.jp>
> wrote:
> >
> >> >> Because newly added node is likely to have out of sync databases.
> Thus
> >> >> bringing it online immediately will allow user to use obsolete
> >> >> databases. You should do online recovery first.
> >> >>
> >> >
> >> > Since the new slave being added is configured using streaming
> >> replication,
> >> > it is lagging behind the master just as much as any other currently
> >> > configured slave. So from that standpoint the new slave should be
> allowed
> >> to
> >> > serve queries.
> >>
> >> It will be possible with pgpool-II 3.1 (without resetting existing
> >> connections).
> >>
> >
> > Is there something in the works to enable this, or is this feature still
> in
> > design phase? If it is already being/been developed, I wish to know if
> this
> > can be back-patched to a point release of pgpool 3.0.x.
>
> It has been already in pgpool-II 3.1 alpha version.
> Currently there's no plan to back-patching to 3.0.x.
>

Can you please point to the CVS versions that I can look at to see if these
can be back patched.

<removing pgpool-general from CC, as it doesn't seem relevant there anymore>

Thanks,
-- 
Gurjeet Singh
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-hackers/attachments/20110730/19dba442/attachment.html>