Search Postgresql Archives

Postgresql C extension and SIGSEGV

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

We are planning to add a C extension (https://github.com/petropavel13/pg_rrule) to our shared postgresql cluster, and wondering what are the risk? (looking for the worst case scenario here)

If there is a SIGSEGV, SIGBUS, SIGABRT ..., is the whole server stopping, or just the request?

Knowing that the extension is only used in select statement, is there a risk of (on disk) data corruption?

Is the risk limited to the current database? (the extension will only be used by 1 application with 1 database, and we prefer not to impact other applications/databases)

Are there any techniques to limit/mitigate these risks? (configuration/compile flags/...)

Thanks in advance
Etienne

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux