Build/install 32 bit ODBC on 64 bit RHEL Linux ?

No help on google, and I don't see anything obvious in configure or the Makefiles...

I can build 32 bit psqlODBC on 32 bit linux, and 64 bit psqlODBC on 64 bit linux, and all runs well. 
Now someone wants to run a 32 bit app on 64 bit Linux. Does anyone know how to force configure to 
build/install a 32 bit psqlODBC library on 64 bit (Red Hat) Linux ? Ditto for unixODBC, if anyone knows.

TIA,
Dean Arnold
Presicient Corp.

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Server memory exhausted on ODBC 8.3.0400

Hi,

Last weekend, I update 2 customers servers with the latest Postgresql 
8.3.5 vrsion. The databases in each customer have +/- 50GB  of data.

I changed some ODBCs versions in clients machines from 7.3.0208 to 8.3.0400.
In this machines, when I run some reports (thats run million of small 
queries), the Postgresql server crashes because this processes use all 
physical and swap memory in the server.

If I disable both 'Use declare/fetch' and 'Updatable Cursor', the error 
does not occurs. I don't need the 'Updatable Cursors', but the 'Use 
Declare Fetch' is crucial to me.
In ODBC 7.3.0208, with this option enabled, the error doesn't occurs.

I think that use of memory grows in sort operations (If I reduce the 
work_mem, the memory grows not so fast). But the queries are too fast 
(average 0.005 ms). I think that after the query is executed, the work 
memory should be released.

Is SAVEPOINT/RELEASE statements generated by ODBC 8.3.0400 (and not 
generated by 7.3) the cause of the problem ???

Best regards,

Alexandre

Server 1:
Debian 4.0 etch
Postgresql 8.3.5 compiled from sources.

Re: Server memory exhausted on ODBC 8.3.0400

alepaes - aldeia digital wrote:
> Hi,
> 
> Last weekend, I update 2 customers servers with the latest Postgresql 
> 8.3.5 vrsion. The databases in each customer have +/- 50GB  of data.
> 
> I changed some ODBCs versions in clients machines from 7.3.0208 to 
> 8.3.0400.
> In this machines, when I run some reports (thats run million of small 
> queries), the Postgresql server crashes because this processes use all 
> physical and swap memory in the server.
> 
> If I disable both 'Use declare/fetch' and 'Updatable Cursor', the error 
> does not occurs. I don't need the 'Updatable Cursors', but the 'Use 
> Declare Fetch' is crucial to me.
> In ODBC 7.3.0208, with this option enabled, the error doesn't occurs.

Does your code close the statements used in the applications?

regards,
Hiroshi Inoue

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: Server memory exhausted on ODBC 8.3.0400

Hi Hiroshi,

Hiroshi Inoue wrote:
> alepaes - aldeia digital wrote:
>> Hi,
>>
>> Last weekend, I update 2 customers servers with the latest Postgresql 
>> 8.3.5 vrsion. The databases in each customer have +/- 50GB  of data.
>>
>> I changed some ODBCs versions in clients machines from 7.3.0208 to 
>> 8.3.0400.
>> In this machines, when I run some reports (thats run million of small 
>> queries), the Postgresql server crashes because this processes use all 
>> physical and swap memory in the server.
>>
>> If I disable both 'Use declare/fetch' and 'Updatable Cursor', the 
>> error does not occurs. I don't need the 'Updatable Cursors', but the 
>> 'Use Declare Fetch' is crucial to me.
>> In ODBC 7.3.0208, with this option enabled, the error doesn't occurs.
> 
> Does your code close the statements used in the applications?

Basically, the program starts with a BEGIN and make a lot of simple 
SELECT queries and some insert and update queries. After this we have a 
COMMIT. Very simple.
Like I sad, If I disable "Use declare" and "Updatable", the error does 
not occurs. If I enable one of this, the error occurs. I test in some 
other heavy applications and the error persists. If I run this in an 
older ODBC driver, everything if fine.

Re: ODBC WINDOWS VISTA ULTIMATE 64 BITS

> Buenos dias,
>
> Estoy necesitando el psqlodbc o el drivers para instalar el odbc para
> windows vista ultimate.
>
> Agradeceria su valios colaboracion.
>
> Cordialmente,
>
>
> LEONARDO LOPEZ L.
>

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: Server memory exhausted on ODBC 8.3.0400

alepaes - aldeia digital wrote:
> Hi Hiroshi,
> 
> Hiroshi Inoue wrote:
>> alepaes - aldeia digital wrote:
>>> Hi,
>>>
>>> Last weekend, I update 2 customers servers with the latest Postgresql 
>>> 8.3.5 vrsion. The databases in each customer have +/- 50GB  of data.
>>>
>>> I changed some ODBCs versions in clients machines from 7.3.0208 to 
>>> 8.3.0400.
>>> In this machines, when I run some reports (thats run million of small 
>>> queries), the Postgresql server crashes because this processes use 
>>> all physical and swap memory in the server.
>>>
>>> If I disable both 'Use declare/fetch' and 'Updatable Cursor', the 
>>> error does not occurs. I don't need the 'Updatable Cursors', but the 
>>> 'Use Declare Fetch' is crucial to me.
>>> In ODBC 7.3.0208, with this option enabled, the error doesn't occurs.
>>
>> Does your code close the statements used in the applications?
> 
> Basically, the program starts with a BEGIN and make a lot of simple 
> SELECT queries and some insert and update queries. After this we have a 
> COMMIT. Very simple.

What kind of tool are you using?
Do you close cursors before "COMMIT" using SQLCloseCursor() or
the coressponding command in your tool?

Re: Server memory exhausted on ODBC 8.3.0400

Hiroshi Inoue wrote:
> alepaes - aldeia digital wrote:
>> Hi Hiroshi,
>>
>> Hiroshi Inoue wrote:
>>> alepaes - aldeia digital wrote:
>>>> Hi,
>>>>
>>>> Last weekend, I update 2 customers servers with the latest 
>>>> Postgresql 8.3.5 vrsion. The databases in each customer have +/- 
>>>> 50GB  of data.
>>>>
>>>> I changed some ODBCs versions in clients machines from 7.3.0208 to 
>>>> 8.3.0400.
>>>> In this machines, when I run some reports (thats run million of 
>>>> small queries), the Postgresql server crashes because this processes 
>>>> use all physical and swap memory in the server.
>>>>
>>>> If I disable both 'Use declare/fetch' and 'Updatable Cursor', the 
>>>> error does not occurs. I don't need the 'Updatable Cursors', but the 
>>>> 'Use Declare Fetch' is crucial to me.
>>>> In ODBC 7.3.0208, with this option enabled, the error doesn't occurs.
>>>
>>> Does your code close the statements used in the applications?
>>
>> Basically, the program starts with a BEGIN and make a lot of simple 
>> SELECT queries and some insert and update queries. After this we have 
>> a COMMIT. Very simple.
> 
> What kind of tool are you using?

where can i find ODBC test cases for postgre odbc driver

ODBC Setup Dialog: "Couldn't load libpq - SSL mode is unavailable"

Hello!

I tried to set up the "PostgreSQL Unicode" ODBC driver 
(psqlodbc_08_03_0400 - msi or dll package) under Windows XP.
On two computers the ODBC Setup Dialog contains the error message 
"Couldn't load libpq - SSL mode is unavailable".
How do I get SSL to work (=get rid of this message)?

What I found out on myself (but didn't help):
libpq.dll depends on msvcr80.dll which was missing, but installing the 
MSVC2008 Redistributable Package didn't made it to work - neither did 
copying msvcr80.dll into the directory of libpq.dll
The Microsoft Dependency Walker Tool doesn't show any missing DLLs for 
libpq.dll - but the message in the ODBC Setup Dialog remains.

Might downgrading to an older version solve this problem?

Best regards,
JKorth

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: ODBC Setup Dialog: "Couldn't load libpq - SSL mode is unavailable"

JKorth wrote:
> Hello!
> 
> I tried to set up the "PostgreSQL Unicode" ODBC driver 
> (psqlodbc_08_03_0400 - msi or dll package) under Windows XP.
> On two computers the ODBC Setup Dialog contains the error message 
> "Couldn't load libpq - SSL mode is unavailable".
> How do I get SSL to work (=get rid of this message)?
> 
> What I found out on myself (but didn't help):
> libpq.dll depends on msvcr80.dll which was missing, but installing the 
> MSVC2008 Redistributable Package didn't made it to work - neither did 
> copying msvcr80.dll into the directory of libpq.dll

Maybe MSVC2005 redistributable package is needed.
Did you try
http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
?

regards,
Hiroshi Inoue

--

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc