From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | gilsonlasco(at)yahoo(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6663: 64bit *conn not handled properly by PQfinish |
Date: | 2012-05-30 01:08:07 |
Message-ID: | 4FC572F7.4050503@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 05/24/2012 11:14 AM, gilsonlasco(at)yahoo(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6663
> Logged by: Gilson Lasco
> Email address: gilsonlasco(at)yahoo(dot)com
> PostgreSQL version: 9.1.3
> Operating system: Linux Ubuntu 12.04 x64
> Description:
>
> while PQconnectdb returns addresses below 2gb, PQfinish works nicely.
> First conn obj above 2gb line and PGfinish segfaults.
Backtrace? Minimal test program to demonstrate the problem?
Did you compile libpq yourself, or is it a packaged version? If
packaged, from where?
What compiler options were used in the build of libpq? and of your program?
Does more than one thread ever access libpq at a time? There are strict
threading rules around how you can access libpq and connections. See the
documentation. If you violate them, you enter undefined behavior territory.
If you run your test program under valgrind, do you see any issues?
> using libpq.a with a C multithread program
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2012-05-30 02:13:24 | Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2 |
Previous Message | Bruce Momjian | 2012-05-30 00:44:07 | Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2 |