Hi Mark,
Thanks again for the info.
I shall create diff sets of indexes and see the query execution time.
And one of such tables might get around 700,000 records over a period of 4-5
months. So what kind of other measures I need to focus on.
I thought of the following
1) Indexes
2) Better Hardware
On Thu, 2008-08-21 at 12:33 +0530, Kranti K K Parisa™ wrote:
> On Wed, Aug 20, 2008 at 8:54 PM, Matthew Wakeling
> <[EMAIL PROTECTED]> wrote:
> On Wed, 20 Aug 2008, Kranti K K Parisa™ wrote:
> creating multiple indexes on same column will effect
> performanc
Thanks Matthew,
does that mean i can just have index1, index3, index4?
On Wed, Aug 20, 2008 at 8:54 PM, Matthew Wakeling <[EMAIL PROTECTED]>wrote:
> On Wed, 20 Aug 2008, Kranti K K Parisa™ wrote:
>
>> creating multiple indexes on same column will effect performance?
>> for example:
>>
>> index1
Thanks Mark,
We are using DBCP and i found something about pgpool in some forum threads,
which gave me queries on it. But I am clear now.
On Wed, Aug 20, 2008 at 8:59 PM, Mark Lewis <[EMAIL PROTECTED]> wrote:
> Yes, we use connection pooling. As I recall Hibernate ships with c3p0
> connection p
Yes, we use connection pooling. As I recall Hibernate ships with c3p0
connection pooling built-in, which is what we use. We were happy enough
with c3p0 that we ended up moving our other non-hibernate apps over to
it, away from DBCP.
pgpool does connection pooling at a socket level instead of in
The tradeoffs for multiple indexes are more or less as follows:
1. Having the right indexes makes queries faster, often dramatically so.
2. But more indexes makes inserts/updates slower, although generally not
dramatically slower.
3. Each index requires disk space. With several indexes, you can
On Wed, 20 Aug 2008, Kranti K K Parisa™ wrote:
creating multiple indexes on same column will effect performance?
for example:
index1 : column1, column2, column3
index2: column1
index3: column2,
index4: column3
index5: column1,column2
The sole purpose of indexes is to affect performance.
Howe
creating multiple indexes on same column will effect performance?
for example:
index1 : column1, column2, column3
index2: column1
index3: column2,
index4: column3
index5: column1,column2
which means, i am trying fire the SQL queries keeping columns in the where
conditions. and the possibilities
The only thing thats bitten me about hibernate + postgres is that when
inserting into partitioned tables, postgres does not reply with the number
of rows that hibernate expected. My current (not great) solution is to
define a specific SQLInsert annotation and tell it not to do any checking
like so
Hi Mark,
Thank you very much for the information. I will analyse the DB structure and
create indexes on PG directly.
Are you using any connection pooling like DBCP? or PG POOL?
Regards, KP
On Wed, Aug 20, 2008 at 8:05 PM, Mark Lewis <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-08-20 at 17:55 +053
On Wed, 2008-08-20 at 17:55 +0530, Kranti K K Parisa™ wrote:
> Hi,
>
> Can anyone suggest the performance tips for PostgreSQL using
> Hibernate.
>
> One of the queries:
>
> - PostgreSQL has INDEX concept and Hibernate also has Column INDEXes.
> Which is better among them? or creating either of t
Hi,
Can anyone suggest the performance tips for PostgreSQL using Hibernate.
One of the queries:
- PostgreSQL has INDEX concept and Hibernate also has Column INDEXes. Which
is better among them? or creating either of them is enough? or need to
create both of them?
and any more performace aspects
12 matches
Mail list logo
