Message-ID: <0de7002c83377e9a0066dc9877c4e1892119289c.camel@cybertec.at>
Subject: Re: how to conveniently upgrade with specific catalog change
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: ZongtianHou <zongtianhou@icloud.com>, pgsql-admin
	 <pgsql-admin@postgresql.org>
Date: Thu, 09 Jul 2020 16:35:20 +0200
In-Reply-To: <0CC0149C-CD15-4A81-B4F1-5AF8E67E57FD@icloud.com>
References: <99E3D554-1D96-42F0-9647-B7D2CECB3E7E@icloud.com>
	 <1647744.1592576042@sss.pgh.pa.us>
	 <0CC0149C-CD15-4A81-B4F1-5AF8E67E57FD@icloud.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Thu, 2020-07-09 at 17:55 +0800, ZongtianHou wrote:
> I am doing some development based on postgres(8.x.x) and encountered a problem when doing upgrade. Normally, there are two ways for me to do upgrade.
>         1. when new version without catalog change, I can replace the binary and restart the cluster.
>         2. when new version with catalog change like add a column or a row to a system table, I can replace
>            the binary and turn allow_system_table_mods to all, do all the changes, then restart.
> 
> But, when new version add a new built-in datatype, like json, which will insert a row in pg_type with specific oid,
> I can not find a simple way to do this. I look up the initdb code, it run the postgres program in bootstrap mode,
> feed it data from postgres.bki file which support oid specification. Simplify the question, How can I do upgrade
> conveniently if I just need to insert one row in one system table with specific oid? Can I do it in upgrade mode
> somehow or I need to run some upgrade program?