RE: A recent message added to pg_upgade - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: A recent message added to pg_upgade
Date
Msg-id TYAPR01MB58660A2306ADD9745C81E30FF5A1A@TYAPR01MB5866.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: A recent message added to pg_upgade  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
Dear Bharath,

> Will the check_hook approach work correctly?

I tested by using the first version and worked well (rejected). Please see the
log which recorded the output and log. Below lines were copied from server
log and found that max_slot_wal_keep_size must not be >= 0.

```
waiting for server to start....2023-10-30 08:53:32.529 GMT [6903] FATAL:  invalid value for parameter
"max_slot_wal_keep_size":1
 
 stopped waiting
pg_ctl: could not start serve
```

> I haven't checked that by
> myself, but I see InitializeGUCOptions() getting called before
> IsBinaryUpgrade is set to true and the passed-in config options ('c')
> are parsed.

I thought the key point was that user-defined options are aligned after the "-b".
User-defined options are set after the '-b'  option, so check_hook could work
as we expected. Thought?

Best Regards,
Hayato Kuroda
FUJITSU LIMITED


Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: A recent message added to pg_upgade
Next
From: "Ryo Matsumura (Fujitsu)"
Date:
Subject: RE: PATCH: document for regression test forgets libpq test