Re: pg_resetwal --next-transaction-id may cause database failed to restart. - Mailing list pgsql-hackers

From movead.li@highgo.ca
Subject Re: pg_resetwal --next-transaction-id may cause database failed to restart.
Date
Msg-id 2020070711224162555318@highgo.ca
Whole thread Raw
In response to Re: pg_resetwal --next-transaction-id may cause database failed torestart.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: pg_resetwal --next-transaction-id may cause database failed to restart.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers

 >ISTM that a reasonable compromise is that if you use -x (or -c, -m, -O)
>and the input value is outside the range supported by existing files,
>then it's a fatal error; unless you use --force, which turns it into
>just a warning.
I do not think '--force' is a good choice, so I add a '--test, -t' option to
force to write a unsafe value to pg_control.
Do you think it is an acceptable method?



Regards,
Highgo Software (Canada/China/Pakistan)
URL : www.highgo.ca
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca
Attachment

pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: Implementing Incremental View Maintenance
Next
From: 曾文旌
Date:
Subject: Re: [Proposal] Global temporary tables