Re: PostgreSQL Process memory architecture - Mailing list pgsql-hackers

From Atri Sharma
Subject Re: PostgreSQL Process memory architecture
Date
Msg-id CAOeZVieEo2O=DMY26ZDMPzWOeVds28uS+4rtxgohobR3Ctafmw@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Process memory architecture  ("Ben Zeev, Lior" <lior.ben-zeev@hp.com>)
Responses Re: PostgreSQL Process memory architecture  ("Ben Zeev, Lior" <lior.ben-zeev@hp.com>)
Re: PostgreSQL Process memory architecture  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Mon, May 27, 2013 at 6:02 PM, Ben Zeev, Lior <lior.ben-zeev@hp.com> wrote:
> Hi Stephen,
>
> The case which I'm seeing is that I have an empty table without any rows,
> Create table test (
>   Num Integer,
>   C1 character varying(512),
>   C2 character varying(512),
>   C3 character varying(512));
>
> I create several partial indexes on this table:
>
> Create index(index_1_c1) on test(c1) where Num=1;
> Create index(index_2_c1) on test(c1) where Num=2;
> Create index(index_1_c2) on test(c1) where Num=1;
> Create index(index_2_c2) on test(c1) where Num=2;


It is just a hunch, but all of your attributes are character varying.
Could TOAST be an issue here?

Regards,

Atri


--
Regards,

Atri
l'apprenant



pgsql-hackers by date:

Previous
From: "Ben Zeev, Lior"
Date:
Subject: Re: PostgreSQL Process memory architecture
Next
From: "Ben Zeev, Lior"
Date:
Subject: Re: PostgreSQL Process memory architecture