| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | sorin(dot)turda(at)syncreon(dot)com |
| Cc: | PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #13956: ODBC driver has a memory leak with TIMESTAMP(0) |
| Date: | 2016-02-16 04:15:58 |
| Message-ID: | CAB7nPqTD7a=+_d5Ofm5hre5CqZ5Jk8JPEyT5Gunh48rJoQzjEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-odbc |
On Sun, Feb 14, 2016 at 1:12 AM, <sorin(dot)turda(at)syncreon(dot)com> wrote:
> Bug reference: 13956
> Logged by: Sorin Turda
> Email address: sorin(dot)turda(at)syncreon(dot)com
> PostgreSQL version: 9.3.9
> Operating system: Windows
> Description:
>
> I converted two tables from Oracle to Postgres
> One of the tables has a field TIMESTAMP(0) and the application ran out of
> memory after 36milion inserts.
> The other table does not cause increasing of working set as shown by
> Resource Manager.
This is better if reported to pgsql-odbc as $subject says that it is a
leak in ODBC itself, so email forwarded. You would need to tell as
well the version of the Postgres ODBC driver you have been using (not
the PostgreSQL server version).
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | miha.vrhovnik | 2016-02-16 09:13:11 | BUG #13963: pg_clusterupgrade and materialized view |
| Previous Message | nick.bales | 2016-02-15 22:29:48 | BUG #13962: transaction logs growing on standby |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Inoue, Hiroshi | 2016-02-16 14:07:01 | Re: Degradation of performance when upgrade psqlodbc to 09.03.0400 |
| Previous Message | Dang Minh Huong | 2016-02-16 03:40:24 | Re: Degradation of performance when upgrade psqlodbc to 09.03.0400 |