Re: BUG #13985: Segmentation fault on PREPARE TRANSACTION

Andres Freund wrote
> Hi,
>
> On 2016-02-24 12:58:24 +0000,

> chris.tessels@

> wrote:
>
>> Core was generated by `postgres: mailinfo_ow mailinfo_ods
>> 10.50.6.6(4188'.
>> Program terminated with signal 11, Segmentation fault.
>>
>> #0 MinimumActiveBackends (min=50) at procarray.c:2472
>> 2472 if (pgxact->xid == InvalidTransactionId)
>>
>
> Could you get us a full backtrace here? It's interesting that you're in
> an XLogFlush()...
>
>> Postgresql version:
>> commit_delay 50 configuration file
>> commit_siblings 50 configuration file
>
> FWIW, these look unlikely to be beneficial. How did you end up with
> those parameters?
>
>
> Greetings,
>
> Andres Freund
>
>
> --
> Sent via pgsql-bugs mailing list (

> pgsql-bugs@

> )
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

Hi Andres,

The full backtrace:

Core was generated by `postgres: mailinfo_subscription_ow mailinfo_subsc'.
Program terminated with signal 11, Segmentation fault.
#0 MinimumActiveBackends (min=50) at procarray.c:2472
2472 if (pgxact->xid == InvalidTransactionId)
(gdb) bt
#0 MinimumActiveBackends (min=50) at procarray.c:2472
#1 0x00000000004c5bfb in XLogFlush (record=79323083800) at xlog.c:2856
#2 0x00000000004bea27 in EndPrepare (gxact=0x7fc2ccf22a00) at
twophase.c:1125
#3 0x00000000004b6b02 in PrepareTransaction () at xact.c:2222
#4 0x00000000004b6e07 in CommitTransactionCommand () at xact.c:2738
#5 0x0000000000685719 in finish_xact_command () at postgres.c:2437
#6 0x00000000006899b0 in exec_execute_message (argc=<value optimized out>,
argv=<value optimized out>, dbname=0x24e2c30 "mailinfo_subscription_ods",
username=<value optimized out>) at postgres.c:1974
#7 PostgresMain (argc=<value optimized out>, argv=<value optimized out>,
dbname=0x24e2c30 "mailinfo_subscription_ods", username=<value optimized
out>) at postgres.c:4142
#8 0x0000000000634929 in BackendRun (argc=<value optimized out>,
argv=<value optimized out>) at postmaster.c:4285
#9 BackendStartup (argc=<value optimized out>, argv=<value optimized out>)
at postmaster.c:3948
#10 ServerLoop (argc=<value optimized out>, argv=<value optimized out>) at
postmaster.c:1679
#11 PostmasterMain (argc=<value optimized out>, argv=<value optimized out>)
at postmaster.c:1287
#12 0x00000000005cc248 in main (argc=3, argv=0x24b87e0) at main.c:228

I'm not sure why we deviated from the default settings for 'commit_delay'
and 'commit_siblings'.
I went through our documentation and could not find an entry why this
setting was changed.
We are running a test with the default settings to see if this has any
impact.

Regards, Chris

--
View this message in context: http://postgresql.nabble.com/BUG-13985-Segmentation-fault-on-PREPARE-TRANSACTION-tp5889158p5889384.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.