From: | Pavel Golub <pavel(at)microolap(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Andrew Chernow <ac(at)esilo(dot)com>, Pavel Golub <pavel(at)microolap(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-interfaces <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] PQdeleteTuple function in libpq |
Date: | 2011-06-02 15:07:30 |
Message-ID: | 1003921930.20110602180730@gf.microolap.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
Hello, Alvaro.
You wrote:
AH> Excerpts from Andrew Chernow's message of jue jun 02 10:12:40 -0400 2011:
>> > Andrew, why we have PQmakeEmptyPGresult, PQcopyResult,
>> > PQsetResultAttrs, PQsetvalue and PQresultAlloc in this case? Of course
>> > there's no big deal with their absence but let's be consistent.
>>
>> I'm not entirely sure what you are trying to do, but can't you use
>> PQmakeEmptyPGresult, PQsetResultAttrs and PQsetvalue to construct a
>> result that excludes the tuples you don't want followed by a
>> PQclear(initial_result)?
AH> Seems pretty wasteful if you want to delete a single tuple from a large
AH> result. I think if you desired to compact the result to free some
AH> memory after deleting a large fraction of the tuples in the result it
AH> could be useful to do that, otherwise just live with the unused holes in
AH> the storage area as suggested by Pavel.
Totally! Thanks Alvaro.
--
With best wishes,
Pavel mailto:pavel(at)gf(dot)microolap(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-06-02 15:10:00 | Re: pgpool versus sequences |
Previous Message | Alvaro Herrera | 2011-06-02 15:02:08 | Re: [HACKERS] PQdeleteTuple function in libpq |
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2011-06-02 15:33:28 | Re: PQdeleteTuple function in libpq |
Previous Message | Alvaro Herrera | 2011-06-02 15:02:08 | Re: [HACKERS] PQdeleteTuple function in libpq |