| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Range Types, constructors, and the type system |
| Date: | 2011-06-30 16:29:37 |
| Message-ID: | 1309451377.10707.137.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2011-06-30 at 09:11 +0200, Florian Pflug wrote:
> > How would the system catalogs be initialized under that theory: surely
> > you're not going to seed (nr. of types) * (nr. of collations) * (nr. of
> > opclasses) range types in initdb?
>
> There's CREATE RANGE.
Right. In that respect, it's more like a record type: many possible
record types exist, but you only define the ones you want.
> By default, no range types would exists I believe.
I was planning to include _some_ by default. Probably not text ranges,
but integer and timestamp[tz] ranges. If nothing else, it makes it
easier to document.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2011-06-30 16:34:18 | Re: Range Types, constructors, and the type system |
| Previous Message | Alvaro Herrera | 2011-06-30 16:00:34 | Re: creating CHECK constraints as NOT VALID |