| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
| Cc: | 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 14:52:19 |
| Message-ID: | 20101007145219.GU26232@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:
> Which kind of information are you thinking about?
> I think that the stuff you put into the CHECK condition for the table
> will say it all.
The problem is that CHECK conditions can contain just about anything,
hence the planner needs to deal with that possibility.
> Infact there you have not just the column names with relevant values, but the
> actual expression(s) to be checked,
Yes, that would be the problem. Proving something based on expressions
is alot more time consuming and complicated than being explicitly told
what goes where.
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincenzo Romano | 2010-10-07 15:03:40 | Re: On Scalability |
| Previous Message | Vincenzo Romano | 2010-10-07 14:44:34 | Re: On Scalability |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincenzo Romano | 2010-10-07 15:03:40 | Re: On Scalability |
| Previous Message | Merlin Moncure | 2010-10-07 14:49:27 | Re: Runtime dependency from size of a bytea field |