From: | Mohsen Bande <mohsenbande(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Postgresql 12 Beta2 Crashes for any Insert/Update |
Date: | 2019-06-30 12:47:37 |
Message-ID: | CAFdu22pKAAsz4z7piJ24=qeqkt_7s99rKZUgwTm+4a6qVOW-Mg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)gmail(dot)com> 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.
> Thanks
>
> On Thu, Jun 27, 2019 at 9:40 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
>> On Thu, Jun 27, 2019 at 1:28 AM Mohsen Bande <mohsenbande(at)gmail(dot)com>
>> 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
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2019-06-30 17:45:03 | Re: "Time of latest checkpoint" stays too old on both master and slave |
Previous Message | Mohsen Bande | 2019-06-30 10:59:38 | Re: Postgresql 12 Beta2 Crashes for any Insert/Update |