Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> Bruce Momjian writes:
> >>> + Exclusion constraints ensure that if any two rows are compared on
> >>> + the specified columns or expressions using the specified operators,
> >>> + at least one of these operator compariso
Bruce Momjian writes:
> Tom Lane wrote:
>> Bruce Momjian writes:
>>> + Exclusion constraints ensure that if any two rows are compared on
>>> + the specified columns or expressions using the specified operators,
>>> + at least one of these operator comparisons will be false. The syntax
Tom Lane wrote:
> Bruce Momjian writes:
> > + Exclusion constraints ensure that if any two rows are compared on
> > + the specified columns or expressions using the specified operators,
> > + at least one of these operator comparisons will be false. The syntax
> > is:
>
> Isn't that
Bruce Momjian writes:
> + Exclusion constraints ensure that if any two rows are compared on
> + the specified columns or expressions using the specified operators,
> + at least one of these operator comparisons will be false. The syntax is:
Isn't that phrasing outright incorrect? Con
Takahiro Itagaki wrote:
>
> "Robert Haas" wrote:
>
> > > * (seq_page_cost/(random_page_cost))
> > > * EXCLUDE constraints has no tags to be linked.
> > > * "EXCLUDE constraints" is not indexed from the Index page.
>
> > CREATE TABLE ... CONSTRAINT ... EXCLUDE rather than CREATE TABLE
> > CONSTR
Takahiro Itagaki wrote:
>
> "Robert Haas" wrote:
>
> > > * (seq_page_cost/(random_page_cost))
> > > * EXCLUDE constraints has no tags to be linked.
> > > * "EXCLUDE constraints" is not indexed from the Index page.
>
> > CREATE TABLE ... CONSTRAINT ... EXCLUDE rather than CREATE TABLE
> > CONSTR
Alvaro Herrera wrote:
>
> Also, where are we on using full names rather than first names only? I
> don't see the point in omitting the last names. Are we trying to
> obscure to outsiders who is really working on our code?
You are the third person to ask for this and I was holding up that
change
On Wed, Mar 31, 2010 at 8:23 PM, Bruce Momjian wrote:
> Robert Haas wrote:
>> On Wed, Mar 31, 2010 at 8:19 PM, Bruce Momjian wrote:
>> >> * "EXCLUDE constraints" is not indexed from the Index page.
>> >> Should we have for it? Unique Constraints have a section for them:
>> >> http://developer.pos
Robert Haas wrote:
> On Wed, Mar 31, 2010 at 8:19 PM, Bruce Momjian wrote:
> >> * "EXCLUDE constraints" is not indexed from the Index page.
> >> Should we have for it? Unique Constraints have a section for them:
> >> http://developer.postgresql.org/pgdocs/postgres/ddl-constraints.html#AEN2431
> >
On Wed, Mar 31, 2010 at 8:21 PM, Bruce Momjian wrote:
> Kevin Grittner wrote:
>> Robert Haas wrote:
>>
>> > I thought it was referring to all pairs of rows, but I see
>> > now it's referring to pairs of columns, so it's correct.
>>
>> If it confused you, I suspect it will confuse others. Offhand
Kevin Grittner wrote:
> Robert Haas wrote:
>
> > I thought it was referring to all pairs of rows, but I see
> > now it's referring to pairs of columns, so it's correct.
>
> If it confused you, I suspect it will confuse others. Offhand,
> I can't see how to improve the language, though.
I hav
On Wed, Mar 31, 2010 at 8:19 PM, Bruce Momjian wrote:
>> * "EXCLUDE constraints" is not indexed from the Index page.
>> Should we have for it? Unique Constraints have a section for them:
>> http://developer.postgresql.org/pgdocs/postgres/ddl-constraints.html#AEN2431
>
> I am unclear if exclude rea
Takahiro Itagaki wrote:
> Hi, I have some questions about 9.0 release note.
> I'd like to work for some of them if required. Comments welcome.
>
> * Allow per-tablespace sequential and random page cost variables
> (seq_page_cost/(random_page_cost)) via ALTER TABLESPACE ... SET/RESET
That is a b
* Kevin Grittner [100331 13:18]:
> If it confused you, I suspect it will confuse others. Offhand,
> I can't see how to improve the language, though.
How about a simple:
s/these/the colomn or expression/
Leaving:
... not all of the column or expression comparisons ...
"These" isn't
Robert Haas wrote:
> I thought it was referring to all pairs of rows, but I see
> now it's referring to pairs of columns, so it's correct.
If it confused you, I suspect it will confuse others. Offhand,
I can't see how to improve the language, though.
-Kevin
--
Sent via pgsql-hackers maili
On Wed, Mar 31, 2010 at 1:07 PM, Kevin Grittner
wrote:
> Robert Haas wrote:
>
>> This says:
>>
>> Exclusion constraints ensure that that if any two rows are
>> compared on the specified column(s) or expression(s) using the
>> specified operator(s), not all of these comparisons will return
>> TRUE
Robert Haas wrote:
> This says:
>
> Exclusion constraints ensure that that if any two rows are
> compared on the specified column(s) or expression(s) using the
> specified operator(s), not all of these comparisons will return
> TRUE.
>
> I think that's backwards - the last clause should say "n
On Wed, Mar 31, 2010 at 2:56 AM, Takahiro Itagaki
wrote:
>
> "Robert Haas" wrote:
>
>> > * (seq_page_cost/(random_page_cost))
>> > * EXCLUDE constraints has no tags to be linked.
>> > * "EXCLUDE constraints" is not indexed from the Index page.
>
>> CREATE TABLE ... CONSTRAINT ... EXCLUDE rather t
On 31 March 2010 07:56, Takahiro Itagaki wrote:
>
> "Robert Haas" wrote:
>
>> > * (seq_page_cost/(random_page_cost))
>> > * EXCLUDE constraints has no tags to be linked.
>> > * "EXCLUDE constraints" is not indexed from the Index page.
>
>> CREATE TABLE ... CONSTRAINT ... EXCLUDE rather than CREAT
"Robert Haas" wrote:
> > * (seq_page_cost/(random_page_cost))
> > * EXCLUDE constraints has no tags to be linked.
> > * "EXCLUDE constraints" is not indexed from the Index page.
> CREATE TABLE ... CONSTRAINT ... EXCLUDE rather than CREATE TABLE
> CONSTRAINT ... EXCLUDE.
Here is a patch to fix
Also, where are we on using full names rather than first names only? I
don't see the point in omitting the last names. Are we trying to
obscure to outsiders who is really working on our code?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company
On Tue, Mar 30, 2010 at 1:37 AM, Takahiro Itagaki
wrote:
> Hi, I have some questions about 9.0 release note.
> I'd like to work for some of them if required. Comments welcome.
>
> * Allow per-tablespace sequential and random page cost variables
> (seq_page_cost/(random_page_cost)) via ALTER TABLE
Hi, I have some questions about 9.0 release note.
I'd like to work for some of them if required. Comments welcome.
* Allow per-tablespace sequential and random page cost variables
(seq_page_cost/(random_page_cost)) via ALTER TABLESPACE ... SET/RESET
^^
Are those
23 matches
Mail list logo
