meta user
network profile
| bio | website | debiki.com |
|---|---|---|
| location | Sweden | |
| age | 33 | |
| visits | member for | 1 year, 5 months |
| seen | Apr 23 at 13:36 | |
| stats | profile views | 4 |
Software developer, building a hopefully better discussion system for blogs and forums.
|
Apr 23 |
awarded | Popular Question |
|
Sep 9 |
awarded | Commentator |
|
Sep 9 |
accepted | PostgreSQL streaming replication broken: invalid magic number, out-of-sequence timeline ID |
|
Sep 9 |
comment |
PostgreSQL streaming replication broken: invalid magic number, out-of-sequence timeline ID Since I don't remember much about the issue, and since you've suggested a reasonable explanation, I'll accept your answer as the correct one. (Otherwise I'll never be able to accept any answer, and the question will be open forever, since I don't remember much about what happened or didn't happen). Thanks |
|
Sep 9 |
comment |
PostgreSQL streaming replication broken: invalid magic number, out-of-sequence timeline ID Concerning "Perhaps the slave was promoted to a master briefly and then demoted again". When I did the failover tests, Initially I didn't know about the recovery_target_timeline parameter, and lots of failover attempts failed and I did the failover again and again. I don't know if this might have demoted and promoted the original master, but it seems reasonable that it could have happened. |
|
Sep 9 |
comment |
PostgreSQL streaming replication broken: invalid magic number, out-of-sequence timeline ID Thanks for your input on the gcc bug and Postgres version 9.1 |
|
Sep 9 |
comment |
PostgreSQL streaming replication broken: invalid magic number, out-of-sequence timeline ID Thanks Chris for your answer! Regrettably I don't remember much about this issue. Half a year later, or so, (that is, one year ago), I did a failover to another mahcine, and everything been working okay since. (As part of the failover I overwrote all/most old files) |
|
Feb 3 |
comment |
Which file is PostgreSQL log file 0? Any chance I accidentally mixed two different versions? -- I don't think so: I've run pg_controldata on the master and slave databases, the output is identical. Also they are the same Amazon EC2 images, and use the same PostgreSQL repo. |
|
Feb 3 |
comment |
Which file is PostgreSQL log file 0? Concerning the error message: This is a streaming replication standby database, and I recently removed recovery_target_timeline = 'latest', and then everything started to work again. (It syncs with the master database, no invalid magic number error no more). Perhaps PostgreSQL for some weird reason used the wrong timeline and found that log file, which for some reason is corrupt. Oddly enough, after PostgreSQL in some way re-synced with the master, everything works although I've now re-added recovery_target_timeline = 'latest'. |
|
Feb 3 |
accepted | Which file is PostgreSQL log file 0? |
|
Feb 3 |
comment |
Which file is PostgreSQL log file 0? Hi Magnus, Thanks! |
|
Jan 29 |
asked | Which file is PostgreSQL log file 0? |
|
Jan 28 |
awarded | Editor |
|
Jan 28 |
revised |
PostgreSQL streaming replication broken: invalid magic number, out-of-sequence timeline ID Add more info on problem |
|
Jan 28 |
comment |
PostgreSQL streaming replication broken: invalid magic number, out-of-sequence timeline ID @Hz.Root: You mean run date in Bash? Did that and dates match. Copying file 000000020000000000000001 to the standby node might work, but I'd rather not do that without actually knowing what the problem is. I suppose the problem will reappear after a while unless I really fix it. Thanks anyway :-) |
|
Jan 21 |
asked | PostgreSQL streaming replication broken: invalid magic number, out-of-sequence timeline ID |
|
Dec 10 |
accepted | PostgreSQL replication: out-of-sequence timeline ID, when former master made slave |
|
Dec 7 |
answered | PostgreSQL replication: out-of-sequence timeline ID, when former master made slave |
|
Dec 6 |
asked | PostgreSQL replication: out-of-sequence timeline ID, when former master made slave |
|
Dec 3 |
awarded | Supporter |
