proposal: operator exclusion constraints with cardinality

Поиск
Список
Период
Сортировка
Искать
От
Jeff Davis
Тема
proposal: operator exclusion constraints with cardinality
Дата
Msg-id
1257119697.27737.214.camel@jdavis
Список
Дерево обсуждения
proposal: operator exclusion constraints with cardinality Jeff Davis <pgsql@j-davis.com>
Re: proposal: operator exclusion constraints with cardinality Tom Lane <tgl@sss.pgh.pa.us>
Re: proposal: operator exclusion constraints with cardinality Jeff Davis <pgsql@j-davis.com>
Re: proposal: operator exclusion constraints with cardinality Robert Haas <robertmhaas@gmail.com>
Re: proposal: operator exclusion constraints with cardinality Jeff Davis <pgsql@j-davis.com>
I have completed the open issues (that I'm aware of) for operator
exclusion constraints:

http://archives.postgresql.org/message-id/1257101600.27737.159.camel@jdavis

I'd now like to propose an extension to that feature: cardinality
limits.

It could go something like this (syntax still open for discussion, for
illustration only):
 EXCLUSION (room     CHECK WITH =,            attendee CHECK WITH =,            during   CHECK WITH &&)   CARDINALITY 30

To mean that at most 30 attendees can be signed up for the same room at
overlapping times.

I have hacked up a basic prototype just to make sure the semantics can
work reasonably well. I haven't implemented the syntax or catalog
changes yet, but the basic semantics with a hard-coded cardinality seem
to hold up.

Thoughts?

Regards,Jeff Davis


В списке pgsql-hackers по дате отправления
От: Jeff Davis
Дата:
От: Itagaki Takahiro
Дата:
Сообщение: Re: Syntax for partitioning
FAQ