Re: PostgreSQL Process memory architecture

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: "Ben Zeev, Lior" <lior(dot)ben-zeev(at)hp(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL Process memory architecture
Date: 2013-05-27 12:39:27
Message-ID: CAOeZVieEo2O=DMY26ZDMPzWOeVds28uS+4rtxgohobR3Ctafmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 27, 2013 at 6:02 PM, Ben Zeev, Lior <lior(dot)ben-zeev(at)hp(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ben Zeev, Lior 2013-05-27 12:41:17 Re: PostgreSQL Process memory architecture
Previous Message Ben Zeev, Lior 2013-05-27 12:32:21 Re: PostgreSQL Process memory architecture