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 12:28:25
Message-ID: CA+TgmoaTJ7RADRvfs69+q42KaUaRGmL=P_VcHCTk=n1+7gM7-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Mar 18, 2025 at 12:36 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> > Cool. The commit message refers to 003_char_signedness, but the test
> > name is 005, not 003.
>
> Thank you for reviewing the patch. I've pushed the patch after fixing it.

Thanks for taking care of it (and so quickly!).

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2025-03-18 12:56:08 pgsql: Make it possible for loadable modules to add EXPLAIN options.
Previous Message Peter Eisentraut 2025-03-18 10:34:51 pgsql: Add some opfamily support functions to lsyscache.c

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2025-03-18 12:42:44 Re: Adding support for SSLKEYLOGFILE in the frontend
Previous Message vignesh C 2025-03-18 12:25:07 Re: Add missing tab completion for VACUUM and ANALYZE with ONLY option