Re: pg_resetwal --next-transaction-id may cause database failed to restart.

From: "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca>
To: "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_resetwal --next-transaction-id may cause database failed to restart.
Date: 2020-07-07 03:22:46
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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?

Highgo Software (Canada/China/Pakistan)
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca

Attachment Content-Type Size
pg_resetwal_transaction_limit_v2.patch application/octet-stream 4.6 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message 曾文旌 2020-07-07 03:47:16 Re: [Proposal] Global temporary tables
Previous Message Andy Fan 2020-07-07 03:11:08 Re: Implementing Incremental View Maintenance