Hi Michael, Alvaro, Tom: Really appreciate yours help, this is an invalid report, and I'm sorry for that.
After I examine restart script, I found we generate recovery.conf every time, and this cause lost of timeline. Thanks. 2018-03-14 23:29 GMT+08:00 Tom Lane <t...@sss.pgh.pa.us>: > Alvaro Herrera <alvhe...@alvh.no-ip.org> writes: > > 彭昱傑 wrote: > >> Every time I restart postgre server, it generates a new history file: > > > That's strange -- it shouldn't happen ... sounds like you're causing a > > crash each time you restart. Are you using immediate mode in shutdown > > maybe? If so, don't; use fast mode instead. > > I'm confused by this report too. Plain crashes shouldn't result in > forking a new timeline. To check, I tried "-m immediate", as well as > "kill -9 postmaster", and neither of those resulted in a new .history file > on restart. I wonder if the OP's restart process involves calling > pg_resetxlog or something like that (which would be risky as heck). > > regards, tom lane >
