On 07/03/2017 04:58 AM, Craig Ringer wrote:
On 3 July 2017 at 03:12, Andres Freund wrote:
Hi,
On 2017-07-02 20:58:52 +0200, Michal Novotný wrote:
thank you all for your advice. I've been investigating this a little more
and finally it turned out it's not a bug in libpq although I got confus
On 07/02/2017 09:12 PM, Andres Freund wrote:
Hi,
On 2017-07-02 20:58:52 +0200, Michal Novotný wrote:
thank you all for your advice. I've been investigating this a little more
and finally it turned out it's not a bug in libpq although I got confused
by going deep as several libpq functions. Th
On 3 July 2017 at 03:12, Andres Freund wrote:
> Hi,
>
> On 2017-07-02 20:58:52 +0200, Michal Novotný wrote:
>> thank you all for your advice. I've been investigating this a little more
>> and finally it turned out it's not a bug in libpq although I got confused
>> by going deep as several libpq fu
Hi all,
thank you all for your advice. I've been investigating this a little more
and finally it turned out it's not a bug in libpq although I got confused
by going deep as several libpq functions. The bug was really on our side
after trying to use connection pointer after calling PQfinish(). The c
Hi,
On 2017-07-02 20:58:52 +0200, Michal Novotný wrote:
> thank you all for your advice. I've been investigating this a little more
> and finally it turned out it's not a bug in libpq although I got confused
> by going deep as several libpq functions. The bug was really on our side
> after trying
On Thu, Jun 29, 2017 at 9:12 AM, Tom Lane wrote:
> Merlin Moncure writes:
>> On Thu, Jun 29, 2017 at 8:23 AM, Michal Novotny
>> wrote:
>>> Could you please help me based on information provided above?
>
>> You might want to run your code through some analysis tools (for
>> example, valgrind).
>
Merlin Moncure writes:
> On Thu, Jun 29, 2017 at 8:23 AM, Michal Novotny
> wrote:
>> Could you please help me based on information provided above?
> You might want to run your code through some analysis tools (for
> example, valgrind).
Yeah, that's what I was about to suggest. pqexpbuffer.c is
On Thu, Jun 29, 2017 at 8:23 AM, Michal Novotny
wrote:
> Hi,
>
> comments inline ...
>
>
>
> On 06/29/2017 03:08 PM, Merlin Moncure wrote:
>>
>> On Thu, Jun 29, 2017 at 4:01 AM, Michal Novotny
>> wrote:
>>>
>>> Hi all,
>>>
>>> we've developed an application using libpq to access a table in the Pg
Hi,
comments inline ...
On 06/29/2017 03:08 PM, Merlin Moncure wrote:
On Thu, Jun 29, 2017 at 4:01 AM, Michal Novotny
wrote:
Hi all,
we've developed an application using libpq to access a table in the PgSQL
database but we're sometimes experiencing segmentation fault on
resetPQExpBuffer() f
On Thu, Jun 29, 2017 at 4:01 AM, Michal Novotny
wrote:
> Hi all,
>
> we've developed an application using libpq to access a table in the PgSQL
> database but we're sometimes experiencing segmentation fault on
> resetPQExpBuffer() function of libpq called from PQexecParams() with
> prepared query.
Hi all,
we've developed an application using libpq to access a table in the
PgSQL database but we're sometimes experiencing segmentation fault on
resetPQExpBuffer() function of libpq called from PQexecParams() with
prepared query.
PostgreSQL version is 9.6.3 and the backtrace is:
Core was g
11 matches
Mail list logo
