Postgresql C extension and SIGSEGV

From: Etienne Champetier <champetier(dot)etienne(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Postgresql C extension and SIGSEGV
Date: 2015-09-03 08:30:50
Message-ID: CAOdf3gr3vWzzsN9picDRMhJu4aOytPoYwKEjtn=tWBO6vnDzTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message krish050591 2015-09-03 10:15:02 pg_stats_repoter error message
Previous Message Sachin Srivastava 2015-09-03 06:39:53 pg_basebackup problem for Streaming replication