From: | Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | PostgreSQL extension API? Documentation? |
Date: | 2016-02-27 13:37:46 |
Message-ID: | 56D1A6AA.6080303@8kdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi.
I have a newbie question for extension development. Extensions
provide an entry point, and are dynamically linked to PostgreSQL. But
what APIs/functions are really available for extensions to call?
The most obvious API is SPI. You could also implements hooks. Of
course, functions, types, aggregates, whatever. But can an extension
call other "internal" PostgreSQL functions? Is there any restriction to
what could --or should-- call an extension? Is there any specific API,
or any documentation which states what is available to use?
In other words: what is the API surface exposed by PostgreSQL to
extension developers? The assumption is that no PostgreSQL code should
be modified, just adding your own and calling existing funcitons.
Thanks,
Álvaro
--
Álvaro Hernández Tortosa
-----------
8Kdata
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2016-02-27 13:38:14 | Re: [COMMITTERS] pgsql: Respect TEMP_CONFIG when running contrib regression tests. |
Previous Message | Michael Paquier | 2016-02-27 13:20:42 | Re: Proposal: "Causal reads" mode for load balancing reads without stale data |