[COMMITTERS] pgsql: Fix mishandling of equivalence-class tests in parameterized plan

Fix mishandling of equivalence-class tests in parameterized plans. Given a three-or-more-way equivalence class, such as X.Y = Y.Y = Z.Z, it was possible for the planner to omit one of the quals needed to enforce that all members of the equivalence class are actually equal. This only happened in th

[COMMITTERS] pgsql: Fix mishandling of equivalence-class tests in parameterized plan

Fix mishandling of equivalence-class tests in parameterized plans. Given a three-or-more-way equivalence class, such as X.Y = Y.Y = Z.Z, it was possible for the planner to omit one of the quals needed to enforce that all members of the equivalence class are actually equal. This only happened in th

[COMMITTERS] pgsql: Fix mishandling of equivalence-class tests in parameterized plan

Fix mishandling of equivalence-class tests in parameterized plans. Given a three-or-more-way equivalence class, such as X.Y = Y.Y = Z.Z, it was possible for the planner to omit one of the quals needed to enforce that all members of the equivalence class are actually equal. This only happened in th

[COMMITTERS] pgsql: Fix mishandling of equivalence-class tests in parameterized plan

Fix mishandling of equivalence-class tests in parameterized plans. Given a three-or-more-way equivalence class, such as X.Y = Y.Y = Z.Z, it was possible for the planner to omit one of the quals needed to enforce that all members of the equivalence class are actually equal. This only happened in th

[COMMITTERS] pgsql: Fix mishandling of equivalence-class tests in parameterized plan

Fix mishandling of equivalence-class tests in parameterized plans. Given a three-or-more-way equivalence class, such as X.Y = Y.Y = Z.Z, it was possible for the planner to omit one of the quals needed to enforce that all members of the equivalence class are actually equal. This only happened in th

[COMMITTERS] pgsql: Add a few entries to the tail of time mapping, to see old values

Add a few entries to the tail of time mapping, to see old values. Without a few entries beyond old_snapshot_threshold, the lookup would often fail, resulting in the more aggressive pruning or vacuum being skipped often enough to matter. This was very clearly shown by a python test script posted b

Re: [COMMITTERS] pgsql: Support building with Visual Studio 2015

Andrew Dunstan wrote: > Support building with Visual Studio 2015 > > Adjust the way we detect the locale. As a result the minumum Windows > version supported by VS2015 and later is Windows Vista. Add some tweaks > to remove new compiler warnings. Remove documentation references to the > now obsole

[COMMITTERS] pgsql: Fix comment whitespace in VS2105 patch

Fix comment whitespace in VS2105 patch per gripe from Michael Paquier. Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/eac3e16741e81c478ce0716683a72e7acc520c4a Modified Files -- src/include/port/win32.h | 2 +- 1 file changed, 1 insertion(+), 1 del

[COMMITTERS] pgsql: Fix comment whitespace in VS2105 patch

Fix comment whitespace in VS2105 patch per gripe from Michael Paquier. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/d34e7b2812467279b95060a4db8d9f4fc4be0e40 Modified Files -- src/include/port/win32.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-

[COMMITTERS] pgsql: doc: Minor wording changes

doc: Minor wording changes From: Dmitry Igrishin Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/82881b2b432c9433b45abc96acf49d5d690eb918 Modified Files -- doc/src/sgml/trigger.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- Sent v

[COMMITTERS] pgsql: Fix typo

Fix typo Author: Thomas Munro Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/a03bda323b0713aeaacfd0050be76df9e6b06a13 Modified Files -- src/include/storage/dsm_impl.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers m

[COMMITTERS] pgsql: Fix typo in VS2015 patch

Fix typo in VS2015 patch reported by Christian Ullrich Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/7dc549238eabe6a634af3e24520f2c3f5667f76f Modified Files -- src/port/win32env.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsq

[COMMITTERS] pgsql: Fix typo in VS2015 patch

Fix typo in VS2015 patch reported by Christian Ullrich Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/b71b4d8528d67198c190294d16bee8df66e42eb9 Modified Files -- src/port/win32env.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent v

Re: [COMMITTERS] pgsql: Support building with Visual Studio 2015

On 04/29/2016 09:29 AM, Christian Ullrich wrote: * Andrew Dunstan wrote: Support building with Visual Studio 2015 http://git.postgresql.org/pg/commitdiff/da52474f3d3cbdf38d8a6677a4ebedaf402ade3a diff --git a/src/port/win32env.c b/src/port/win32env.c index 7e4ff62..d6b0ebe 100644 (file) --

Re: [COMMITTERS] pgsql: Support building with Visual Studio 2015

* Andrew Dunstan wrote: Support building with Visual Studio 2015 http://git.postgresql.org/pg/commitdiff/da52474f3d3cbdf38d8a6677a4ebedaf402ade3a diff --git a/src/port/win32env.c b/src/port/win32env.c index 7e4ff62..d6b0ebe 100644 (file) --- a/src/port/win32env.c +++ b/src/port/win32env.c @@ -

[COMMITTERS] pgsql: Support building with Visual Studio 2015

Support building with Visual Studio 2015 Adjust the way we detect the locale. As a result the minumum Windows version supported by VS2015 and later is Windows Vista. Add some tweaks to remove new compiler warnings. Remove documentation references to the now obsolete msysGit. Michael Paquier, some

[COMMITTERS] pgsql: Support building with Visual Studio 2015

Support building with Visual Studio 2015 Adjust the way we detect the locale. As a result the minumum Windows version supported by VS2015 and later is Windows Vista. Add some tweaks to remove new compiler warnings. Remove documentation references to the now obsolete msysGit. Michael Paquier, some

Re: [COMMITTERS] pgsql: Reserve the "pg_" namespace for roles

Bruce, On Friday, April 29, 2016, Bruce Momjian wrote: > On Fri, Apr 8, 2016 at 08:56:34PM +, Stephen Frost wrote: > > Reserve the "pg_" namespace for roles > > > > This will prevent users from creating roles which begin with "pg_" and > > will check for those roles before allowing an upgra

Re: [COMMITTERS] pgsql: Reserve the "pg_" namespace for roles

On Fri, Apr 8, 2016 at 08:56:34PM +, Stephen Frost wrote: > Reserve the "pg_" namespace for roles > > This will prevent users from creating roles which begin with "pg_" and > will check for those roles before allowing an upgrade using pg_upgrade. > > This will allow for default roles to be p

Re: [COMMITTERS] pgsql: Fix support of digits in email/hostnames.

On Fri, Apr 29, 2016 at 06:43:04AM -0400, Bruce Momjian wrote: > On Fri, Apr 29, 2016 at 01:20:35PM +0300, Teodor Sigaev wrote: > > >Doesn't this invalidate tsvector indexes upgraded by pg_upgrade? Should > > >they be marked as invalid? > > Directly, it affects on functional indexes i.e. over to_t

Re: [COMMITTERS] pgsql: Fix support of digits in email/hostnames.

On Fri, Apr 29, 2016 at 01:20:35PM +0300, Teodor Sigaev wrote: > >Doesn't this invalidate tsvector indexes upgraded by pg_upgrade? Should > >they be marked as invalid? > Directly, it affects on functional indexes i.e. over to_tsvector(). But it > affects tsvector column, it should be recreated if

Re: [COMMITTERS] pgsql: Fix support of digits in email/hostnames.

Doesn't this invalidate tsvector indexes upgraded by pg_upgrade? Should they be marked as invalid? Directly, it affects on functional indexes i.e. over to_tsvector(). But it affects tsvector column, it should be recreated if it was generated by ts_vector() function. Can you also fix the oth