Re: PostgreSQL giving jitters to Skypak

Hi !

I think it would be a good idea to check how they are using indexes, and
what the structure of the database is. Missing an index or two can
affect quite much.

Rgs,

Jussi

> Dear Josh ,
>
> >>http://www.cxotoday.com/cxo/jsp/index.jsp?log=false&file=template1.jsp§
>
>>ion_code=1&section=News&storyid=1383&subsection_code=1&subsection=Business&s
> >>ource=cxtnl&userid=aspire420(at)hotpop(dot)com
> >>
> >>
> >
> >Can you or someone else in India contact them? Shridhar?
> >
> >
> >
> I would do this and following is the list of questions I would be asking
> on the same time I would request others to add more ,
>
> 1. Vacuum usage
> 2. postgresql.conf settings used (I am not a pro in this field)
> 3. OS used its not clear if PostgreSQL is on non windows platform.
> 4. I myself am not aware of any consultants in India that can provide
> PostgreSQL optimization.
>
> Others are requested to add more questions I would be calling on 27
> August 2004, on the following number
> 22-28508181
>
> Best Regards,
> Vishal Kashyap
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

On Tue, 24 Aug 2004, Jussi(dot)Mikkola(at)bonware(dot)com wrote:

> Hi !
>
> I think it would be a good idea to check how they are using indexes, and
> what the structure of the database is. Missing an index or two can
> affect quite much.

My interest is in the type of hard drive interface, the drive(s) capacity
and utilization and the size of the database. There is no mention in the
article and though we on the list know better than to use IDE in
(database) servers I've seen plenty of systems from major manufacturers
come with IDE.

Rod
--
"Open Source Software - You usually get more than you pay for..."
"Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"

On Tue, 24 Aug 2004, Jussi(dot)Mikkola(at)bonware(dot)com wrote:

> Hi !
>
> I think it would be a good idea to check how they are using indexes, and what
> the structure of the database is. Missing an index or two can affect quite
> much.

As I'm experiencing with a client right now ... schema hurts alot too ...
all of their queries are bigint = int, so they are having to go through
their code and changing it to bigint = int::bigint so that indices are
being used properly ...

> > Rgs,
>
> Jussi
>
>
>> Dear Josh ,
>>
>> >>http://www.cxotoday.com/cxo/jsp/index.jsp?log=false&file=template1.jsp§
>>
>>> ion_code=1&section=News&storyid=1383&subsection_code=1&subsection=Business&s
>> >>ource=cxtnl&userid=aspire420(at)hotpop(dot)com
>> >> >>
>> >
>> >Can you or someone else in India contact them? Shridhar?
>> >
>> > >
>> I would do this and following is the list of questions I would be asking on
>> the same time I would request others to add more ,
>>
>> 1. Vacuum usage
>> 2. postgresql.conf settings used (I am not a pro in this field)
>> 3. OS used its not clear if PostgreSQL is on non windows platform.
>> 4. I myself am not aware of any consultants in India that can provide
>> PostgreSQL optimization.
>>
>> Others are requested to add more questions I would be calling on 27 August
>> 2004, on the following number
>> 22-28508181
>>
>> Best Regards,
>> Vishal Kashyap
>>
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
>From pgsql-advocacy-owner(at)postgresql(dot)org Tue Aug 24 22:07:04 2004
X-Original-To: pgsql-advocacy-postgresql(dot)org(at)localhost(dot)postgresql(dot)org
Received: from localhost (unknown [200.46.204.144])
by svr1.postgresql.org (Postfix) with ESMTP id 84CDA5E46E9
for <pgsql-advocacy-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>; Tue, 24 Aug 2004 22:07:03 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
with ESMTP id 57881-09
for <pgsql-advocacy-postgresql(dot)org(at)localhost(dot)postgresql(dot)org>;
Wed, 25 Aug 2004 01:06:56 +0000 (GMT)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.194])
by svr1.postgresql.org (Postfix) with ESMTP id A8A3B5E46C2
for <pgsql-advocacy(at)postgresql(dot)org>; Tue, 24 Aug 2004 22:06:53 -0300 (ADT)
Received: by mproxy.gmail.com with SMTP id 75so78891rnl
for <pgsql-advocacy(at)postgresql(dot)org>; Tue, 24 Aug 2004 18:06:55 -0700 (PDT)
Received: by 10.38.76.76 with SMTP id y76mr1724652rna;
Tue, 24 Aug 2004 18:06:55 -0700 (PDT)
Received: by 10.38.162.23 with HTTP; Tue, 24 Aug 2004 18:06:55 -0700 (PDT)
Message-ID: <59d991c40408241806aafcfd7(at)mail(dot)gmail(dot)com>
Date: Tue, 24 Aug 2004 21:06:55 -0400
From: Christopher Petrilli <petrilli(at)gmail(dot)com>
Reply-To: Christopher Petrilli <petrilli(at)gmail(dot)com>
To: "Marc G. Fournier" <scrappy(at)postgresql(dot)org>
Subject: Re: PostgreSQL giving jitters to Skypak
Cc: "Jussi(dot)Mikkola(at)bonware(dot)com" <jussi(dot)mikkola(at)bonware(dot)com>,
aspire420(at)hotpop(dot)com, pgsql-advocacy(at)postgresql(dot)org,
in(at)postgresql(dot)org
In-Reply-To: <20040824201021(dot)K68447(at)ganymede(dot)hub(dot)org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <17956242(dot)1093376101443(dot)JavaMail(dot)jussi(dot)mikkola(at)bonware(dot)com> <20040824201021(dot)K68447(at)ganymede(dot)hub(dot)org>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 testsX-Spam-Level:
X-Archive-Number: 200408/318
X-Sequence-Number: 5195

On Tue, 24 Aug 2004 20:11:13 -0300 (ADT), Marc G. Fournier
<scrappy(at)postgresql(dot)org> wrote:
> On Tue, 24 Aug 2004, Jussi(dot)Mikkola(at)bonware(dot)com wrote:
>
> > Hi !
> >
> > I think it would be a good idea to check how they are using indexes, and what
> > the structure of the database is. Missing an index or two can affect quite
> > much.
>
> As I'm experiencing with a client right now ... schema hurts alot too ...
> all of their queries are bigint = int, so they are having to go through
> their code and changing it to bigint = int::bigint so that indices are
> being used properly ...

I've always wondered... is there some reason we don't do "type
promotion" to match indices? So if someone provides an int, and a
bigint index exists, it should be used automatically, as they're
interchangable (i.e. int is a subset of bigint).

Chris
--
| Christopher Petrilli
| petrilli(at)gmail(dot)com

Chris,

> I've always wondered... is there some reason we don't do "type
> promotion" to match indices? So if someone provides an int, and a
> bigint index exists, it should be used automatically, as they're
> interchangable (i.e. int is a subset of bigint).

Because it's actually more difficult that it sounds.

However, we *have* made changes to 8.0 to make it better at selecting
appropriate types for constants when and index exists.

--
Josh Berkus
Aglio Database Solutions
San Francisco

On Tue, 24 Aug 2004, Christopher Petrilli wrote:

> On Tue, 24 Aug 2004 20:11:13 -0300 (ADT), Marc G. Fournier
> <scrappy(at)postgresql(dot)org> wrote:
>> On Tue, 24 Aug 2004, Jussi(dot)Mikkola(at)bonware(dot)com wrote:
>>
>>> Hi !
>>>
>>> I think it would be a good idea to check how they are using indexes, and what
>>> the structure of the database is. Missing an index or two can affect quite
>>> much.
>>
>> As I'm experiencing with a client right now ... schema hurts alot too ...
>> all of their queries are bigint = int, so they are having to go through
>> their code and changing it to bigint = int::bigint so that indices are
>> being used properly ...
>
> I've always wondered... is there some reason we don't do "type
> promotion" to match indices? So if someone provides an int, and a
> bigint index exists, it should be used automatically, as they're
> interchangable (i.e. int is a subset of bigint).

This is fixed (or, partially addressed) in 8.0 ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664