On Thu, Oct 12, 2023 at 7:17 AM Amit Kapila <amit.kapil...@gmail.com> wrote: > Now, as mentioned in the first paragraph, it seems we anyway don't > need to reset the WAL at the end when setting the next OID for the new > cluster with the -o option. If that is true, then I think even without > slots work it will be helpful to have such an option in pg_resetwal. > > Thoughts?
I wonder if we should instead provide a way to reset the OID counter with a function call inside the database, gated by IsBinaryUpgrade. Having something like pg_resetwal --but-dont-actually-reset-the-wal seems both self-contradictory and vulnerable to abuse that we might be better off not inviting. -- Robert Haas EDB: http://www.enterprisedb.com