Re: pgsql: pg_upgrade: Preserve default char signedness value from old clus

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Masahiko Sawada <msawada(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: pg_upgrade: Preserve default char signedness value from old clus
Date: 2025-03-18 03:02:14
Message-ID: CA+Tgmoa_JeYU=WxPtZvq1+VVLkgYhYpHAVH967fw0iu_RyMg8g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Mon, Mar 17, 2025 at 6:02 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> I've confirmed the issue and attached a patch to fix it.

Cool. The commit message refers to 003_char_signedness, but the test
name is 005, not 003.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Masahiko Sawada 2025-03-18 04:34:27 pgsql: Fix the test 005_char_signedness.
Previous Message Michael Paquier 2025-03-18 00:41:54 pgsql: psql: Add \sendpipeline to send query buffers while in a pipelin

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2025-03-18 03:18:17 Re: Allow io_combine_limit up to 1MB
Previous Message Corey Huinker 2025-03-18 02:51:27 Re: vacuumdb changes for stats import/export