Re: On Scalability

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: On Scalability
Date: 2010-10-07 15:12:44
Message-ID: 20101007151244.GV26232@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

* Vincenzo Romano (vincenzo(dot)romano(at)notorand(dot)it) wrote:
> I would expect a parser to ... ehm ... parse the CHECK constraint
> expression at "CREATE TABLE " time and
> extract all the needed "high quality metadata", like the list of
> columns involved and the type of
> checks (range, value list, etc.).

Check constraints can be added after the table is created. Inheiritance
can be added/changed independently of check constraints. Hacking all of
the inheiritance, check constraint creation, and any other possibly
involved code paths to try to figure out if this particular table, check
constraint, inheiritance relationship, etc, is part of a partitioning
setup isn't exactly trivial, or the right approach.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2010-10-07 15:15:44 Re: On Scalability
Previous Message Robert Haas 2010-10-07 15:11:16 Re: O_DSYNC broken on MacOS X?

Browse pgsql-performance by date

  From Date Subject
Next Message Stephen Frost 2010-10-07 15:15:44 Re: On Scalability
Previous Message Vincenzo Romano 2010-10-07 15:10:40 Re: On Scalability