On Mon, Aug 2, 2010 at 11:16 PM, Jeff Davis pg...@j-davis.com wrote:
On Mon, 2010-08-02 at 12:27 -0400, Robert Haas wrote:
I was also wondering if it would be worth adding some additional
regression testing to contrib/btree_gist exercising this new
functionality. Thoughts?
Sure. I attached
Robert Haas robertmh...@gmail.com writes:
On Mon, Aug 2, 2010 at 11:16 PM, Jeff Davis pg...@j-davis.com wrote:
Sure. I attached two tests.
Committed.
I see no sign of a commit from here ...
regards, tom lane
--
Sent via pgsql-hackers mailing list
On Tue, Aug 3, 2010 at 3:52 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Mon, Aug 2, 2010 at 11:16 PM, Jeff Davis pg...@j-davis.com wrote:
Sure. I attached two tests.
Committed.
I see no sign of a commit from here ...
Sigh. Forgot to exit my editor.
On Sun, 2010-08-01 at 21:57 -0400, Robert Haas wrote:
On Fri, Jul 16, 2010 at 1:19 AM, Jeff Davis pg...@j-davis.com wrote:
Thank you for the review.
On Mon, 2010-07-12 at 17:17 +0900, Itagaki Takahiro wrote:
(1) Exclusion constraints support for operators where x operator x
is false
On Mon, Aug 2, 2010 at 2:39 AM, Jeff Davis pg...@j-davis.com wrote:
On Sun, 2010-08-01 at 21:57 -0400, Robert Haas wrote:
On Fri, Jul 16, 2010 at 1:19 AM, Jeff Davis pg...@j-davis.com wrote:
Thank you for the review.
On Mon, 2010-07-12 at 17:17 +0900, Itagaki Takahiro wrote:
(1)
On Mon, 2010-08-02 at 12:27 -0400, Robert Haas wrote:
I was also wondering if it would be worth adding some additional
regression testing to contrib/btree_gist exercising this new
functionality. Thoughts?
Sure. I attached two tests.
Regards,
Jeff Davis
***
On Fri, Jul 16, 2010 at 1:19 AM, Jeff Davis pg...@j-davis.com wrote:
Thank you for the review.
On Mon, 2010-07-12 at 17:17 +0900, Itagaki Takahiro wrote:
(1) Exclusion constraints support for operators where x operator x
is false (tiny patch)
2010/7/16 Jeff Davis pg...@j-davis.com:
I'd like to ask you to write additional documentation about btree_gist [1]
that the module will be more useful when it is used with exclusion
constraints together. Without documentation, no users find the usages.
| Example using an Exclusion Constraint
Hi,
Thank you for the review.
On Mon, 2010-07-12 at 17:17 +0900, Itagaki Takahiro wrote:
(1) Exclusion constraints support for operators where x operator x
is false (tiny patch)
https://commitfest.postgresql.org/action/patch_view?id=307
(2) btree_gist support for searching on (not equals)
(1) Exclusion constraints support for operators where x operator x
is false (tiny patch)
https://commitfest.postgresql.org/action/patch_view?id=307
(2) btree_gist support for searching on (not equals)
https://commitfest.postgresql.org/action/patch_view?id=308
Those patches should be committed at
Marko Tiikkaja marko.tiikk...@cs.helsinki.fi wrote:
On 5/21/10 11:47 PM +0300, Jeff Davis wrote:
It also allows you to enforce the constraint that only one tuple exists
in a table by doing something like:
create table a
(
i int,
exclude using gist (i with),
On Sat, 2010-05-22 at 01:02 +0300, Marko Tiikkaja wrote:
On 5/21/10 11:47 PM +0300, Jeff Davis wrote:
It also allows you to enforce the constraint that only one tuple exists
in a table by doing something like:
create table a
(
i int,
exclude using gist (i with),
On Mon, May 24, 2010 at 11:25 PM, Jeff Davis pg...@j-davis.com wrote:
I think the original case (same values only) is potentially useful
enough that we should support it.
+1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-hackers
This patch adds support to btree_gist for searching on (not
equals).
This allows an interesting use of exclusion constraints:
Say you have a table:
create table zoo
(
cage int,
animal text,
exclude using gist (cage with =, animal with )
);
That will permit you to add as
On 5/21/10 11:47 PM +0300, Jeff Davis wrote:
It also allows you to enforce the constraint that only one tuple exists
in a table by doing something like:
create table a
(
i int,
exclude using gist (i with),
unique (i)
);
FWIW, this is achievable a lot more easily:
15 matches
Mail list logo
