I have a case where it seems the planner should be able to infer more
from its partial indexes than it is doing. Observe:
px=# select version();
version
PostgreSQL 8.1.3 on i686-pc-linux-gnu
-Original Message-
From: "Luke Lonergan"<[EMAIL PROTECTED]>
Sent: 19/03/06 16:26:58
To: "Kenji Morishige"<[EMAIL PROTECTED]>, "Claus Guttesen"<[EMAIL PROTECTED]>
Cc: "pgsql-performance@postgresql.org"
Subject: Re: [PERFORM] Best OS & Configuration for Dual Xeon w/4GB &
> I notice that no
So a default value for all products would be size:"all"
for example, the same tshirt shop also sells cdroms.
It size attribute would be to place it to be :"all". (because we cannot
place an uniqe index on null values)
But the industry evolves and so in time the same cdrom is now available for
Kenji,
On 3/17/06 4:08 PM, "Kenji Morishige" <[EMAIL PROTECTED]> wrote:
> Thanks guys, I'm studying each of your responses and am going to start to
> experiement.
I notice that no one asked you about your disk bandwidth - the Adaptec 2200S
is a "known bad" controller - the bandwidth to/from in
On 19/03/06, Andreas Pflug <[EMAIL PROTECTED]> wrote:
> Antoine wrote:
> > On 18/03/06, Andreas Pflug <[EMAIL PROTECTED]> wrote:
> >
> >>Antoine wrote:
> >>
> >>>Hi,
> >>>I have enabled the autovacuum daemon, but occasionally still get a
> >>>message telling me I need to run vacuum when I access a
Antoine wrote:
On 18/03/06, Andreas Pflug <[EMAIL PROTECTED]> wrote:
Antoine wrote:
Hi,
I have enabled the autovacuum daemon, but occasionally still get a
message telling me I need to run vacuum when I access a table in
pgadmin.
Bring up the postgresql.conf editor on that server, and watch
another approach would be:
table product:
productid int8 PK
productname charvar(255)
table versions
productid int8 FK
versionid int8 PK
size
color
...
quantity int4
an example would be then:
table product:
- productid: 123, productname: 'nice cotton t-shirt'
- productid: 442, productname:
We have size and color in the product table itself. It is really an
attribute of the product. If you update the availability of the product
often, I would split out the quantity into a separate table so that you can
truncate and update as needed.
Patrick Hatcher
Development Manager Analytics/MI
Hi,
Is there any work on the cards for implementing other partitioning
strategies? I see mysql 5.1 will have support for hashes and stuff but
didn't see anything in the todos for postgres.
Cheers
Antoine
--
This is where I should put some witty comment.
---(end of broadcast
On 18/03/06, Andreas Pflug <[EMAIL PROTECTED]> wrote:
> Antoine wrote:
> > Hi,
> > I have enabled the autovacuum daemon, but occasionally still get a
> > message telling me I need to run vacuum when I access a table in
> > pgadmin.
>
> pgAdmin notices a discrepancy between real rowcount and estimat
10 matches
Mail list logo
