From: | Andrew Chernow <ac(at)esilo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
Subject: | Re: [PATCHES] libpq events patch (with sgml docs) |
Date: | 2008-09-17 14:37:37 |
Message-ID: | 48D11631.8070709@esilo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Andrew Chernow wrote:
> New patch following our discussion with updated docs.
>
>>> few logical errors). I don't think it makes sense to do it
>>> otherwise, it would be like calling free after a malloc failure.
>>
>> I can live with that definition, but please document it.
>>
>>
>
> To build on this analogy, PGEVT_CONNRESET is like a realloc. Meaning,
> the initial malloc "PGEVT_REGISTER" worked by the realloc
> "PGEVT_CONNRESET" didn't ... you still have free "PGEVT_CONNDESTROY" the
> initial. Its documented that way. Basically if a register succeeds, a
> destroy will always be sent regardless of what happens with a reset.
>
>
I attached the wrong patch. I'm sorry.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
Attachment | Content-Type | Size |
---|---|---|
pgevents.patch | text/plain | 11.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2008-09-17 14:47:01 | Re: Common Table Expressions (WITH RECURSIVE) patch |
Previous Message | Heikki Linnakangas | 2008-09-17 14:36:46 | Re: Autovacuum and Autoanalyze |
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Helmle | 2008-09-17 18:49:00 | Re: still alive? |
Previous Message | Andrew Chernow | 2008-09-17 14:29:23 | Re: [PATCHES] libpq events patch (with sgml docs) |