Re: [HACKERS] Replication status in logical replication

2017-09-25 Thread Masahiko Sawada
On Tue, Sep 26, 2017 at 10:36 AM, Vaishnavi Prabakaran wrote: > Hi, > > On Wed, Sep 13, 2017 at 9:59 AM, Daniel Gustafsson wrote: >> >> >> I’m not entirely sure why this was flagged as "Waiting for Author” by the >> automatic run, the patch applies for me and builds so resetting back to >> “Needs

Re: [HACKERS] Replication status in logical replication

2017-09-25 Thread Vaishnavi Prabakaran
Hi, On Wed, Sep 13, 2017 at 9:59 AM, Daniel Gustafsson wrote: > > I’m not entirely sure why this was flagged as "Waiting for Author” by the > automatic run, the patch applies for me and builds so resetting back to > “Needs > review”. > > This patch applies and build cleanly and I did a testing w

Re: [HACKERS] Replication status in logical replication

2017-09-12 Thread Daniel Gustafsson
> On 30 May 2017, at 19:55, Peter Eisentraut > wrote: > > On 5/29/17 22:56, Noah Misch wrote: >> On Fri, May 19, 2017 at 11:33:48AM +0900, Masahiko Sawada wrote: >>> On Wed, Apr 12, 2017 at 5:31 AM, Simon Riggs wrote: Looks like a bug that we should fix in PG10, with backpatch to 9.4 (or >

Re: [HACKERS] Replication status in logical replication

2017-05-30 Thread Peter Eisentraut
On 5/29/17 22:56, Noah Misch wrote: > On Fri, May 19, 2017 at 11:33:48AM +0900, Masahiko Sawada wrote: >> On Wed, Apr 12, 2017 at 5:31 AM, Simon Riggs wrote: >>> Looks like a bug that we should fix in PG10, with backpatch to 9.4 (or >>> as far as it goes). >>> >>> Objections to commit? >>> >> >> S

Re: [HACKERS] Replication status in logical replication

2017-05-29 Thread Noah Misch
On Fri, May 19, 2017 at 11:33:48AM +0900, Masahiko Sawada wrote: > On Wed, Apr 12, 2017 at 5:31 AM, Simon Riggs wrote: > > On 22 March 2017 at 02:50, Masahiko Sawada wrote: > > > >> When using logical replication, I ran into a situation where the > >> pg_stat_replication.state is not updated unti

Re: [HACKERS] Replication status in logical replication

2017-05-18 Thread Masahiko Sawada
On Wed, Apr 12, 2017 at 5:31 AM, Simon Riggs wrote: > On 22 March 2017 at 02:50, Masahiko Sawada wrote: > >> When using logical replication, I ran into a situation where the >> pg_stat_replication.state is not updated until any wal record is sent >> after started up. For example, I set up logical

Re: [HACKERS] Replication status in logical replication

2017-04-11 Thread Simon Riggs
On 22 March 2017 at 02:50, Masahiko Sawada wrote: > When using logical replication, I ran into a situation where the > pg_stat_replication.state is not updated until any wal record is sent > after started up. For example, I set up logical replication with 2 > subscriber and restart the publisher

[HACKERS] Replication status in logical replication

2017-03-21 Thread Masahiko Sawada
Hi all, When using logical replication, I ran into a situation where the pg_stat_replication.state is not updated until any wal record is sent after started up. For example, I set up logical replication with 2 subscriber and restart the publisher server, but I see the following status for a while

Re: [HACKERS] Replication status

2002-05-30 Thread Andrew Sullivan
On Tue, May 28, 2002 at 06:08:21PM -0700, Thomas Lockhart wrote: > clients. We have been very low-key (imho) in representing this solution > to the developer community, but it should be considered for applications > matching its capabilities. I should like to emphasise that I have no desire to

Re: [HACKERS] Replication status

2002-05-28 Thread Bruce Momjian
Agreed. It would be nice to see both a single-master and multi-master server included in our main tree and a clear description of when to use each. The confusion over the various replication solutions and their strengths/weaknesses is a major problem. I always felt a clearer README for rserv w

Re: [HACKERS] Replication status

2002-05-28 Thread Thomas Lockhart
... > rserver only does single-master, while most people want multi-master. As you probably know, rserv is not limited to only a single instance of a single master. Many replication problems can be described as a "single source" problem (or should be described as such; moving to a fully distribut

Re: [HACKERS] Replication status

2002-05-28 Thread Bruce Momjian
Michael Meskes wrote: > On Mon, May 27, 2002 at 05:12:33PM -0400, Bruce Momjian wrote: > > Last I talked to Darren, the replication code was modified to merge into > > our 7.2 tree. There are still pieces missing so it will not be > > functional when applied. It is remotely possible there could

Re: [HACKERS] Replication status

2002-05-28 Thread Bruce Momjian
Karel Zak wrote: > On Mon, May 27, 2002 at 11:40:20AM -0400, Michael Meskes wrote: > > > could anyone please enlighten me about the status of replication? I do > > expect lots of questions about this, and I'm not really sure if I can > > promise it for 7.3. :-) > > 8.0 ;-) (?) > > I add the o

Re: [HACKERS] Replication status

2002-05-28 Thread Steven Singer
On Tue, 28 May 2002, Michael Meskes wrote: > > This is about pgreplication I think. Is the the replication project of > choice for pgsql? IIRC there quite some projects for this topic: > > PostgreSQL replicator > Rserver > Usogres > dbbalancer There's also DBMirror which I submitted to the co

Re: [HACKERS] Replication status & point-in-time recovery

2002-05-28 Thread Andrew Sullivan
On Tue, May 28, 2002 at 09:53:53AM +0200, Karel Zak wrote: > On Mon, May 27, 2002 at 11:40:20AM -0400, Michael Meskes wrote: > > > could anyone please enlighten me about the status of replication? I do > > expect lots of questions about this, and I'm not really sure if I can > > promise it for 7.

Re: [HACKERS] Replication status

2002-05-28 Thread Karel Zak
On Mon, May 27, 2002 at 11:40:20AM -0400, Michael Meskes wrote: > could anyone please enlighten me about the status of replication? I do > expect lots of questions about this, and I'm not really sure if I can > promise it for 7.3. :-) 8.0 ;-) (?) I add the other quesion: how is current status

Re: [HACKERS] Replication status

2002-05-28 Thread Michael Meskes
On Mon, May 27, 2002 at 05:12:33PM -0400, Bruce Momjian wrote: > Last I talked to Darren, the replication code was modified to merge into > our 7.2 tree. There are still pieces missing so it will not be > functional when applied. It is remotely possible there could be > master-slave in 7.3, but

Re: [HACKERS] Replication status

2002-05-27 Thread Bruce Momjian
Tom Lane wrote: > Michael Meskes <[EMAIL PROTECTED]> writes: > > could anyone please enlighten me about the status of replication? I do > > expect lots of questions about this, and I'm not really sure if I can > > promise it for 7.3. :-) > > Unless 7.3 slips drastically from our current intended

Re: [HACKERS] Replication status

2002-05-27 Thread Darren Johnson
> > > >Unless 7.3 slips drastically from our current intended schedule >(beta in late August), I think it's pretty safe to say there will >be no replication in 7.3, beyond what's already available (rserv >and so forth). > I can't speak for any of the other replication projects, but pgreplication

Re: [HACKERS] Replication status

2002-05-27 Thread Tom Lane
Michael Meskes <[EMAIL PROTECTED]> writes: > could anyone please enlighten me about the status of replication? I do > expect lots of questions about this, and I'm not really sure if I can > promise it for 7.3. :-) Unless 7.3 slips drastically from our current intended schedule (beta in late Augus

[HACKERS] Replication status

2002-05-27 Thread Michael Meskes
Hi, could anyone please enlighten me about the status of replication? I do expect lots of questions about this, and I'm not really sure if I can promise it for 7.3. :-) Yes, I know it's marked urgent in the TODO list, but no one seems to be listed as tackling this topic. Thanks a lot. Michael

[HACKERS] Replication status

2002-05-27 Thread Michael Meskes
Hi, could anyone please enlighten me about the status of replication? I do expect lots of questions about this, and I'm not really sure if I can promise it for 7.3. :-) Yes, I know it#s marked urgent in the TODO list, but no one seems to be listed as tackling this topic. Thanks a lot. Michael