Re: Test to dump and restore objects left behind by regression - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Test to dump and restore objects left behind by regression
Date
Msg-id 202503130842.c5lnhxalynu2@alvherre.pgsql
Whole thread Raw
In response to Re: Test to dump and restore objects left behind by regression  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: Test to dump and restore objects left behind by regression
List pgsql-hackers
Hello

On 2025-Mar-13, Ashutosh Bapat wrote:

> 1. can you please run the test again and share the dump outputs. They
> will be located in a temporary directory with names
> src_dump.sql_adjusted and dest_dump.<format>.sql_adjusted.

Ah, I see the problem :-)  The first initdb does this:

    # Running: initdb -D
/home/alvherre/Code/pgsql-build/master/src/bin/pg_upgrade/tmp_check/t_002_pg_upgrade_old_node_data/pgdata-A trust -N
--wal-segsize1 --allow-group-access --encoding UTF-8 --lc-collate C --lc-ctype C --locale-provider builtin
--builtin-localeC.UTF-8 -k
 
    The files belonging to this database system will be owned by user "alvherre".
    This user must also own the server process.

    The database cluster will be initialized with this locale configuration:
      locale provider:   builtin
      default collation: C.UTF-8
      LC_COLLATE:  C
      LC_CTYPE:    C
      LC_MESSAGES: C
      LC_MONETARY: es_CL.UTF-8
      LC_NUMERIC:  es_CL.UTF-8
      LC_TIME:     es_CL.UTF-8
    The default text search configuration will be set to "english".

    Data page checksums are enabled.

which for some reason used my environment setting for LC_MONETARY.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"But static content is just dynamic content that isn't moving!"
                http://smylers.hates-software.com/2007/08/15/fe244d0c.html



pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: long-standing data loss bug in initial sync of logical replication
Next
From: Amit Kapila
Date:
Subject: Re: Selectively invalidate caches in pgoutput module