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

Re: libpq object hooks (libpq events)

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Andrew Chernow" <ac(at)esilo(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: libpq object hooks (libpq events)
Date: 2008-05-20 17:29:55
Message-ID: b42b73150805201029i5d1dbdcbj7941518c5bc0bf28@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Mon, May 19, 2008 at 8:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Chernow <ac(at)esilo(dot)com> writes:
>> Here is an updated patch for what was called object hooks.  This is now
>> called libpq events.  If someone has a better name or hates ours, let us
>> know.
>
> This is starting to get there,

Interesting you haven't commented on two areas, the actual placement
of the event callers in the libpq code (i'm assuming these are ok),
and the PQcopyResult/PQsetvalue functions.  The latter area introduces
some new behavior into standard libpq (imo) so it deserves some
scrutiny.

merlin

In response to

pgsql-hackers by date

Next:From: Merlin MoncureDate: 2008-05-20 18:03:17
Subject: idea: storing view source in system catalogs
Previous:From: Greg SmithDate: 2008-05-20 17:20:48
Subject: Re: triggers on prepare, commit, rollback... ?

pgsql-patches by date

Next:From: Guillaume LelargeDate: 2008-05-20 20:23:19
Subject: Re: Patch to change psql default banner v6
Previous:From: Bryce NesbittDate: 2008-05-20 15:23:03
Subject: Re: Patch to change psql default banner v6

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