Skip site navigation (1) Skip section navigation (2)

Re: libpq object hooks

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>, "Andrew Chernow" <ac(at)esilo(dot)com>
Subject: Re: libpq object hooks
Date: 2008-05-14 16:21:56
Message-ID: b42b73150805140921v30d24b75m6c230932c61ffdd2@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Wed, May 14, 2008 at 10:44 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm wondering why the hooks need names at all.  AFAICS all that
> libpq needs to know about a hook is a callback function address
> and a void * passthrough pointer.

For reference...here is what libpqtypes has to do to bind via the
hooking interface:
http://libpqtypes.esilo.com/browse_source.html?file=hooks.c

Are you proposing something substantially different (not my handle
suggestion)? How would it work exactly?

merlin

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2008-05-14 16:22:23
Subject: Re: [COMMITTERS] pgsql: Improve logic for finding object files on OBJS lines in contrib
Previous:From: Peter EisentrautDate: 2008-05-14 16:18:34
Subject: Re: Re: [COMMITTERS] pgsql: Improve logic for finding object files on OBJS lines in contrib

pgsql-patches by date

Next:From: Andrew ChernowDate: 2008-05-14 16:34:08
Subject: Re: libpq object hooks
Previous:From: Andrew ChernowDate: 2008-05-14 16:02:17
Subject: Re: libpq object hooks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group