On Thu, Jul 21, 2011 at 12:19 PM, Tom Lane wrote:
> Robert Haas writes:
>> So I finally got around to taking a look at this patch, and I guess my
>> basic feeling is that I like it. The existing code is pretty weird
>> and inconsistent: the logic in PQsetvalue() basically does the same
>> thing
Robert Haas writes:
> So I finally got around to taking a look at this patch, and I guess my
> basic feeling is that I like it. The existing code is pretty weird
> and inconsistent: the logic in PQsetvalue() basically does the same
> thing as the logic in pqAddTuple(), but incompatibly and less
>
On Wed, Jul 20, 2011 at 10:28 PM, Robert Haas wrote:
> On Mon, Jul 18, 2011 at 6:38 AM, Pavel Golub wrote:
>> Hello, Merlin.
>>
>> I hope it's OK that I've added Andrew's patch to CommitFest:
>> https://commitfest.postgresql.org/action/patch_view?id=606
>>
>> I did this becuase beta3 already rele
On Mon, Jul 18, 2011 at 6:38 AM, Pavel Golub wrote:
> Hello, Merlin.
>
> I hope it's OK that I've added Andrew's patch to CommitFest:
> https://commitfest.postgresql.org/action/patch_view?id=606
>
> I did this becuase beta3 already released, but nut nothig is done on
> this bug.
So I finally got
Hello, Merlin.
I hope it's OK that I've added Andrew's patch to CommitFest:
https://commitfest.postgresql.org/action/patch_view?id=606
I did this becuase beta3 already released, but nut nothig is done on
this bug.
You wrote:
MM> On Thu, Jun 23, 2011 at 7:54 AM, Andrew Chernow wrote:
>>> you
Hello.
Any news on these issues? Becuase beta3 is scheduled for July 11th...
You wrote:
MM> On Jun 6
MM> (http://archives.postgresql.org/pgsql-hackers/2011-06/msg00272.php),
MM> Pavel discovered an issue with PQsetvalue that could cause libpq to
MM> wander off into unallocated memory that was pr
On Thu, Jun 23, 2011 at 7:54 AM, Andrew Chernow wrote:
>> you are creating as you iterate through. This behavior was
>> unnecessary in terms of what libpqtypes and friends needed and may (as
>> Tom suggested) come back to bite us at some point. As it turns out,
>> PQsetvalue's operati
2011/6/23 Andrew Chernow
> you are creating as you iterate through. This behavior was
>>unnecessary in terms of what libpqtypes and friends needed and may (as
>>Tom suggested) come back to bite us at some point. As it turns out,
>>PQsetvalue's operation on results that weren't cr
you are creating as you iterate through. This behavior was
unnecessary in terms of what libpqtypes and friends needed and may (as
Tom suggested) come back to bite us at some point. As it turns out,
PQsetvalue's operation on results that weren't created via
PQmakeEmptyResult wa
Hello, Merlin.
You wrote:
MM> On Jun 6
MM> (http://archives.postgresql.org/pgsql-hackers/2011-06/msg00272.php),
MM> Pavel discovered an issue with PQsetvalue that could cause libpq to
MM> wander off into unallocated memory that was present in 9.0.x. A
MM> fairly uninteresting fix was quickly pro
2011/6/23 Merlin Moncure
> On Jun 6 (
> http://archives.postgresql.org/pgsql-hackers/2011-06/msg00272.php),
> Pavel discovered an issue with PQsetvalue that could cause libpq to
> wander off into unallocated memory that was present in 9.0.x. A
> fairly uninteresting fix was quickly produced, but
On Jun 6 (http://archives.postgresql.org/pgsql-hackers/2011-06/msg00272.php),
Pavel discovered an issue with PQsetvalue that could cause libpq to
wander off into unallocated memory that was present in 9.0.x. A
fairly uninteresting fix was quickly produced, but Tom indicated
during subsequent revie
12 matches
Mail list logo
