From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Patches (PostgreSQL) <pgsql-patches@postgresql.org>
Cc: Andrew Chernow <ac@esilo.com>
Subject: Re: libpq object hooks
Date: Thu, 15 May 2008 14:08:03 -0400
Message-ID: <9303.1210874883@sss.pgh.pa.us> (raw)
In-Reply-To: <482C7778.40707@dunslane.net>
References: <b42b73150804301323i18b00019i62e765708abb65aa@mail.gmail.com>
<482A58D8.2030205@dunslane.net>
<20080514043313.GS6966@alvh.no-ip.org>
<482AD896.4000504@dunslane.net>
<19342.1210776271@sss.pgh.pa.us>
<b42b73150805150852m7b3c28fai2d7a4497c84118b2@mail.gmail.com>
<6044.1210867771@sss.pgh.pa.us>
<482C7778.40707@dunslane.net>
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> It might work to use the address of the hook callback function as
>> a key for retrieving the associated void * pointer. You'd need to
>> not register the same callback function more than once per object,
>> but from what I gather here you don't need to.
> Or else have the library return a unique handle when registering hooks,
> rather than supplying a hook name.
Uh, how would that solve your problem? Seems like the difficulty
shifts from "how do I get the hook data" to "how do I get the key
with which to get the hook data".
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-patches@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, mmoncure@gmail.com, alvherre@commandprompt.com, ac@esilo.com
Subject: Re: libpq object hooks
In-Reply-To: <9303.1210874883@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox