Re: Reducing connection overhead in pg_upgrade compat check phase

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Reducing connection overhead in pg_upgrade compat check phase
Date: 2024-02-08 23:04:56
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 8 Feb 2024, at 15:16, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:

> One option could perhaps be to include a version number for <= comparison, and
> if set to zero a function pointer to a version check function must be provided?
> That would handle the simple cases in a single place without messy logic, and
> leave the more convoluted checks with a special case function.

The attached is a draft version of this approach, each check can define to run
for all versions, set a threshold version for which it runs or define a
callback which implements a more complicated check.

Daniel Gustafsson

Attachment Content-Type Size
v13-0001-pg_upgrade-run-all-data-type-checks-per-connecti.patch application/octet-stream 40.3 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2024-02-08 23:22:33 Re: Make documentation builds reproducible
Previous Message Maiquel Grassi 2024-02-08 22:28:29 RE: Psql meta-command conninfo+