| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | AJ Weber <aweber(at)comcast(dot)net> |
| Cc: | Shaun Thomas <sthomas(at)optionshouse(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: how to improve perf of 131MM row table? |
| Date: | 2014-06-26 15:44:18 |
| Message-ID: | CAGTBQpZYBcf1umZcAWO_wE-qJ6uwuksto4RtnswcsAoOZcKmYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jun 26, 2014 at 12:38 PM, AJ Weber <aweber(at)comcast(dot)net> wrote:
> I noticed this too. I am trying to find where the actual SQL is generated,
> and I am seeing if this is an artifact of Hibernate.
>
> Will test the same query without the quotes as you recommend. (But I don't
> know where to fix that, if it is the actual issue, unfortunately.)
Last time I used Hibernate it was an ancient version, but that version
didn't handle bigint very well, IIRC.
What we did is write a customized dialect that did the proper handling
of it. I really can't remember the details, nor whether this still
applies to the latest version. But it's worth a look.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AJ Weber | 2014-06-26 15:48:27 | Re: how to improve perf of 131MM row table? |
| Previous Message | AJ Weber | 2014-06-26 15:38:53 | Re: how to improve perf of 131MM row table? |