Re: pg_upgrade check for invalid role-specific default config

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Charlie Hornsby <charlie(dot)hornsby(at)hotmail(dot)co(dot)uk>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: pg_upgrade check for invalid role-specific default config
Date: 2021-04-13 19:11:38
Message-ID: 3350566.1618341098@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Charlie Hornsby <charlie(dot)hornsby(at)hotmail(dot)co(dot)uk> writes:
> I tested the above patch with the invalid data locally and it avoids
> the restore error that we ran into previously. Also it requires no
> intervention to progress with pg_upgrade unlike my initial idea of
> adding an check, so it is definitely simpler from a user perspective.

Thanks for testing! I've pushed this, so it will be in the May
minor releases.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-04-13 19:59:03 Re: New IndexAM API controlling index vacuum strategies
Previous Message Robert Haas 2021-04-13 18:25:23 Re: [PATCH] Identify LWLocks in tracepoints