| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Inconsistent DB data in Streaming Replication |
| Date: | 2013-04-08 15:52:33 |
| Message-ID: | 14775.1365436353@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Samrat Revagade <revagade(dot)samrat(at)gmail(dot)com> writes:
> We have been trying to figure out possible solutions to the following
> problem in streaming replication Consider following scenario:
> If master receives commit command, it writes and flushes commit WAL records
> to the disk, It also writes and flushes data page related to this
> transaction.
> The master then sends WAL records to standby up to the commit WAL record.
> But before sending these records if failover happens then, old master is
> ahead of standby which is now the new master in terms of DB data leading
> to inconsistent data .
I don't exactly see the problem ... unless you're imagining that master
and slave share the same data storage or something like that. That's
not going to work for a ton of reasons besides this one.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Bohmer | 2013-04-08 15:58:37 | Re: BUG #8043: 9.2.4 doesn't open WAL files from archive, only looks in pg_xlog |
| Previous Message | Shaun Thomas | 2013-04-08 15:50:53 | Re: Inconsistent DB data in Streaming Replication |