Re: Patch: Extend NOT NULL representation to pg_constraint

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: José Arthur Benetasso Villanova <jose(dot)arthur(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Patch: Extend NOT NULL representation to pg_constraint
Date: 2010-09-26 19:18:46
Message-ID: AANLkTikiH=D28ZUo0x56yQPBOUhDOTeXzmu=6_SR35pD@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 26, 2010 at 2:11 PM, Bernd Helmle <mailings(at)oopsware(dot)de> wrote:
> --On 25. September 2010 19:55:02 -0300 José Arthur Benetasso Villanova
> <jose(dot)arthur(at)gmail(dot)com> wrote:
>
>> One thing that I take notice is when you create a simple table like this
>> one: select count(*) from pg_constraint ; 12 rows appears in
>> pg_constraint, 10 to the sequence. Is that ok?
>
> Not sure i get you here, can you elaborate more on this?

I think his question was - how do we feel about the massive catalog
bloat this patch will create?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-09-26 19:24:03 Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Previous Message Magnus Hagander 2010-09-26 19:01:38 Re: Congratulations on leaving CVS