Horton

Re: longfin and tamandua aren't too happy but I'm not sure why

Dilip Kumar <dilipbalaut@gmail.com>

View thread View on postgr.es
From: Dilip Kumar <dilipbalaut@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@lists.postgresql.org, Justin Pryzby <pryzby@telsasoft.com>
Date: 2022-09-28T05:04:15Z
Lists: pgsql-hackers 
wrasse is also failing with a bus error, but I cannot get the stack
trace.  So it seems it is hitting some alignment issues during startup
[1].  Is it possible to get the backtrace or lineno?

[1]
2022-09-28 03:19:26.228 CEST [180:4] LOG:  redo starts at 0/30FE9D8
2022-09-28 03:19:27.674 CEST [177:3] LOG:  startup process (PID 180)
was terminated by signal 10: Bus Error
2022-09-28 03:19:27.674 CEST [177:4] LOG:  terminating any other
active server processes
2022-09-28 03:19:27.677 CEST [177:5] LOG:  shutting down due to
startup process failure
2022-09-28 03:19:27.681 CEST [177:6] LOG:  database system is shut down

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

Commits

  1. meson: Split 'main' suite into 'regress' and 'isolation'

  2. ci: Add 32bit build and test

  3. Fix InitializeRelfilenumberMap for 05d4cbf9b6ba708858984b01ca0fc56d59d4ec7c

  4. Fix alignment problems with SharedInvalSmgrMsg.

  5. In BufTagGetForkNum, cast to the correct type.

  6. Increase width of RelFileNumbers from 32 bits to 56 bits.

  7. Harden pg_filenode_relation test against concurrent DROP TABLE.