On 02/27/16 14:11, Álvaro Hernández Tortosa wrote:
> Why would it be so much work? Creating a function list, and maybe
> documenting those, doesn't sound like a daunting task.
>
> I wouldn't mind volunteering for this work, but I guess I would need
> some help to understand and identify t
On 02/27/16 13:51, Álvaro Hernández Tortosa wrote:
> ... I still lack a list of functions that might be callable (I
> understand not even those labeled with PGDLLIMPORT are all good candidates
> and some good candidates might not be labeled as such) from an extension
> point of view. Have you
Álvaro Hernández Tortosa wrote:
I wouldn't mind volunteering for this work, but I guess I would
need some help to understand and identify the candidate parts of
the API. If anyone could help me here, please let me know.
When you write an extension often regret that someone specified this or
t
On 27/02/16 15:43, Tom Lane wrote:
Chapman Flack writes:
On 02/27/16 08:37, �lvaro Hernández Tortosa wrote:
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
On 27/02/16 15:10, Chapman Flack wrote:
On 02/27/16 08:37, Álvaro Hernández Tortosa wrote:
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 funcito
Chapman Flack writes:
> On 02/27/16 08:37, Ãlvaro Hernández Tortosa wrote:
>> 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.
> That's
On 27/02/16 15:01, Fabrízio de Royes Mello wrote:
On Sat, Feb 27, 2016 at 10:37 AM, Álvaro Hernández Tortosa
mailto:a...@8kdata.com>> wrote:
>
>
> Hi.
>
> I have a newbie question for extension development. Extensions
provide an entry point, and are dynamically linked to PostgreSQL
On 02/27/16 08:37, Álvaro Hernández Tortosa wrote:
> 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.
That's an excellent question that r
On Sat, Feb 27, 2016 at 10:37 AM, Álvaro Hernández Tortosa
wrote:
>
>
> 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
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, func
10 matches
Mail list logo
