After Investigating deeper, I found the root cause.
Actually, the problem exists in certain tables, which i have created a trigger on them calling a function from a custom dynamic extension.
the extension needs to rebuild (make && make install) against new PG development header files.
On Sun, Jun 30, 2019 at 3:29 PM Mohsen Bande <mohsenbande@xxxxxxxxx> wrote:
I've created a new database, and started to copy current data into it. it seems to work.it seems that the problem relates to upgrade process of database catalogs from Beta1 to Beta2.if the problem persists, it will investigate the stacktrace.ThanksOn Thu, Jun 27, 2019 at 9:40 PM Peter Geoghegan <pg@xxxxxxx> wrote:On Thu, Jun 27, 2019 at 1:28 AM Mohsen Bande <mohsenbande@xxxxxxxxx> wrote:
> i have a working database in PG 12 Beta 1. today i upgraded it to Beta 2. everything goes fine and server is up and running. but trying to INSERT/UPDATE anything, server crashes:
Is it possible for you to send us a stacktrace?
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
Thanks
--
Peter Geoghegan
