onstraints ?
That's with version 9.5.3 & 9.6 beta 3.
Thanks,
Jean-Pierre Pelletier
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
The link to download PostgreSQL 9.6 Beta 2 for Windows X64
is not working.
The link does download something, but it's Beta 1.
http://www.enterprisedb.com/products-services-training/pgdownload#windows
Thanks,
Jean-Pierre Pelletier
lt;-> rat');
returns "false"
select to_tsvector('simple', 'cat rat bat fat') @@ to_tsquery('simple',
'cat <-> rat');
returns "true"
Jean-Pierre Pelletier
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, June 8, 2016 1:12 PM
To: Teodor
', 'blue');
Is this expected ?
Thanks,
Jean-Pierre Pelletier
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
IS
DISTINCT FROM old.col1) OR (new.col2 IS DISTINCT FROM old.col2)) OR
((new.col3 IS NOT NULL) AND (new.col3 IS DISTINCT FROM old.col3))) OR
((new.col3 IS NULL) AND (new.col3 IS DISTINCT FROM old.col3 EXECUTE
PROCEDURE f1();
We got these results on Windows x64.
Thanks,
Jean-Pierre Pelletier
f.com/2010/09/25/exclusion-constraints-are-general
ized-sql-unique/
If partitioning could be based on EC, it would bring these additional
benefits:
- The choice of operator as long as it is boolean. commutative and
Indexable
- The use of Expression/Function and not just bare columns
Jean-Pierre
f.com/2010/09/25/exclusion-constraints-are-general
ized-sql-unique/
If partitioning could be based on EC, it would bring these additional
benefits:
- The choice of operator as long as it is boolean. commutative and
Indexable
- The use of Expression/Function and not just bare columns
Jean-Pierre
One use case for this might be with constraint exclusion where there
would be one
partition per collation (language) with queries against the parent table always
being for exactly one language.
Not sure what the collation should be in the parent table then.
--
Sent via pgsql-hackers mailing
AS $$
SELECT
('epoch'::date + s.i * '1 second'::interval)::date AS generate_series
FROM
generate_series(
extract('epoch' FROM $1)::bigint,
extract('epoch' FROM $2)::bigint,
extract('epoch' FROM date_trunc('day', $3))::bigint -- does a floor
) s(i);
$$;
Jean-Pierre Pelletier
e
AS $$
SELECT
('epoch'::date + s.i * '1 second'::interval)::date AS generate_series
FROM
generate_series(
extract('epoch' FROM $1)::bigint,
extract('epoch' FROM $2)::bigint,
extract('epoch' FROM date_trunc('day', $3))::bigint -- does a floor
) s(i);
$$;
Jean-Pierre Pelletier
e
in the
statements displayed with log_min_error_statement.
Is it possible to set log_min_error_statement to display the parameters
value?
Thanks,
Jean-Pierre Pelletier
e-djuster
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
longer form has no problem picking up the index
I could restate the problem as: Why can't the planner handle
col is not distinct from 123 as well as
col is not null and 123 is not null and col = 123 or col is null and 123 is
null
Jean-Pierre Pelletier
From: Martijn van Oosterhout kleptog
with the equivalent
longer forms which
use indexes.
8.2 is better than 8.1 which was not picking up indexes even with the
longer forms.
Jean-Pierre Pelletier
From: Jim C. Nasby [EMAIL PROTECTED]
To: JEAN-PIERRE PELLETIER [EMAIL PROTECTED]
CC: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS
)
Index Cond: (col = 123)
Total runtime: 0.366 ms
(4 rows)
Time: 0.000 ms
I am on Windows XP Service pack 2 with PostgreSQL 8.2 beta2
Thanks,
Jean-Pierre Pelletier
e-djuster
---(end of broadcast)---
TIP 4: Have you searched our list archives
[EMAIL PROTECTED], JEAN-PIERRE PELLETIER
[EMAIL PROTECTED], List pgsql-jdbc@postgresql.org,
PostgreSQL-development pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [JDBC] server process (PID 1188) exited with exit
code
Date: Wed, 25 Oct 2006 03:26:07 +
Tom Lane wrote
Yes, the problem is gone in 8.2 beta2.
Thanks all for an outstanding product and support,
Jean-Pierre Pelletier
From: Tom Lane [EMAIL PROTECTED]
To: JEAN-PIERRE PELLETIER [EMAIL PROTECTED]
CC: pgsql-hackers@postgresql.org, [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [HACKERS] [JDBC
16 matches
Mail list logo