Re: pg_upgrade from Postgresql-12 to Postgresql-13 fails with "Creating dump of database schemas postgres *failure*"

Thank you for the information.

Also, I am wondering about your libraries related to the PostGIS / postgis_raster extension. So, what are the versions of linked GDAL, PROJ, SFCGAL, SPATIALITE libraries?  If you updated the PostGIS extension a while ago, old versions of the libraries may be left. Especially, if there is an incompatible version of the proj, it could be the cause. Please, be sure all libraries linked to the posgis_raster and PostGIS extensions are up to date.

I suppose that the problem always occurred on the second database. For instance, if you run the pg_dump command for the kinta database first and then for the lugano database, the problem will occur for the lugana database, the second database. However, the kinta database will be completed successfully. So, something is happening on the system /* I think because of the bugs of the extensions /* when you run the pg_dump command for a database that has the PostGIS or postgis_raster extension. 

Best,

Liam

Yoong S. Chow <chowy1026@gmail.com>, 20 Şub 2022 Paz, 15:13 tarihinde şunu yazdı:

Hi Liam, 

Here are the answers: 

- on my Postgresql-12, the default version of pgaudit is 1.4.2 but the installed version is 1.4.1. Is this causing a problem?

- for postgis: both default and installed versions are 3.2.1; so are postgis_raster. 

- The postgis and postgis_raster extensions are installed in all other user databases except for postgres, postgis_raster and template1

- TIL about postgresql.auto.conf. Didn't know this file existed. Attached. 

Thanks a lot for your help. 

Best,
Yoong Shin

On Sun, Feb 20, 2022 at 7:52 PM liam saffioti <liam.saffiotti@gmail.com> wrote:

Hi Chow,

Can you answer the below questions, please?

- What is the pgaudit extension version?

- What is the PostGIS and postgis_raster extensions version?

- In which databases are PostGIS or postgis_raster extensions installed?

- Can you add postgresql.auto.conf file?

I suppose that the problem is caused by the extensions bugs.

Best,

Liam

Yoong S. Chow <chowy1026@gmail.com>, 19 Şub 2022 Cmt, 19:02 tarihinde şunu yazdı:

Hi Jeff,

Could you please clarify what core files are? I am truly a newbie to postgresql. 

The pg_dump on both `postgres` and `postgis_raster` databases ran without error.  Attached is the posgtresql log. 

Thank you,
Chow

On Sat, Feb 19, 2022 at 12:07 AM Jeff Janes <jeff.janes@gmail.com> wrote:

On Fri, Feb 18, 2022 at 8:35 AM Yoong S. Chow <chowy1026@gmail.com> wrote:

Here are the logs: pg_upgrade_server.log, pg_upgrade_dump_13427.log and tail_postgresql-12-2022-02-16_190344.log.

From that last log file we have:

1. 2022-02-16 19:04:35 +08 [303982]: [4957-1] session=620cda42.4a36e,user=postgres,db=postgis_raster,app=pg_dump,client=[local] | LOG:  disconnection: session time: 0:00:01.101 user=postgres database=postgis_raster host=[local]
2. free(): invalid pointer

and then a little later:

1. 2022-02-16 19:04:35 +08 [303791]: [7-1] session=620cda0f.4a2af,user=,db=,app=,client= | LOG:  server process (PID 303982) was terminated by signal 6: Aborted

Do you get any core files for 303982?  Do you have core dumps enabled?  What do you get if you run a manual pg_dump -s on db postgis_raster?

Cheers,

Jeff