Refactor check_ functions to use filehandle for status
When reporting failure in check_ functions there is (typically) a text-
file mentioned in the error report which contains further details. Some
check_ functions kept a separate flag variable to indicate failure, and
some just checked the state
doc: Fix typo in user inheritance documentation
Commit 620ac285483 accidentally introduced a typo in the privilege
inheritance documentation
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/c7892c253fdc7bcb99a61e820798588ee4c071b9
Modified Files
--
doc/s
Fix a bug in roles_is_member_of.
Commit e3ce2de09d814f8770b2e3b3c152b7671bcdb83f rearranged this
function to be able to identify which inherited role had admin option
on the target role, but it got the order of operations wrong, causing
the function to return wrong answers in the presence of non-i
In the Snowball dictionary, don't try to stem excessively-long words.
If the input word exceeds 1000 bytes, don't pass it to the stemmer;
just return it as-is after case folding. Such an input is surely
not a word in any human language, so whatever the stemmer might
do to it would be pretty dubio
In the Snowball dictionary, don't try to stem excessively-long words.
If the input word exceeds 1000 bytes, don't pass it to the stemmer;
just return it as-is after case folding. Such an input is surely
not a word in any human language, so whatever the stemmer might
do to it would be pretty dubio
In the Snowball dictionary, don't try to stem excessively-long words.
If the input word exceeds 1000 bytes, don't pass it to the stemmer;
just return it as-is after case folding. Such an input is surely
not a word in any human language, so whatever the stemmer might
do to it would be pretty dubio
In the Snowball dictionary, don't try to stem excessively-long words.
If the input word exceeds 1000 bytes, don't pass it to the stemmer;
just return it as-is after case folding. Such an input is surely
not a word in any human language, so whatever the stemmer might
do to it would be pretty dubio
In the Snowball dictionary, don't try to stem excessively-long words.
If the input word exceeds 1000 bytes, don't pass it to the stemmer;
just return it as-is after case folding. Such an input is surely
not a word in any human language, so whatever the stemmer might
do to it would be pretty dubio
In the Snowball dictionary, don't try to stem excessively-long words.
If the input word exceeds 1000 bytes, don't pass it to the stemmer;
just return it as-is after case folding. Such an input is surely
not a word in any human language, so whatever the stemmer might
do to it would be pretty dubio
In the Snowball dictionary, don't try to stem excessively-long words.
If the input word exceeds 1000 bytes, don't pass it to the stemmer;
just return it as-is after case folding. Such an input is surely
not a word in any human language, so whatever the stemmer might
do to it would be pretty dubio
Fix MSVC warning in compat_informix/rnull.pgc
Building the ecpg tests with MSVC, with warnings enabled, results in the
following warning:
src/interfaces/ecpg/test/compat_informix/rnull.pgc(19,1): warning C4305:
'initializing': truncation from 'double' to 'float'
The more obvious fix would be an
Derive freeze cutoff from nextXID, not OldestXmin.
Before now, the cutoffs that VACUUM used to determine which XIDs/MXIDs
to freeze were determined at the start of each VACUUM by taking related
cutoffs that represent which XIDs/MXIDs VACUUM should treat as still
running, and subtracting an XID/MXI
Prevent long-term memory leakage in autovacuum launcher.
get_database_list() failed to restore the caller's memory context,
instead leaving current context set to TopMemoryContext which is
how CommitTransactionCommand() leaves it. The callers both think
they are using short-lived contexts, for th
Prevent long-term memory leakage in autovacuum launcher.
get_database_list() failed to restore the caller's memory context,
instead leaving current context set to TopMemoryContext which is
how CommitTransactionCommand() leaves it. The callers both think
they are using short-lived contexts, for th
Prevent long-term memory leakage in autovacuum launcher.
get_database_list() failed to restore the caller's memory context,
instead leaving current context set to TopMemoryContext which is
how CommitTransactionCommand() leaves it. The callers both think
they are using short-lived contexts, for th
Prevent long-term memory leakage in autovacuum launcher.
get_database_list() failed to restore the caller's memory context,
instead leaving current context set to TopMemoryContext which is
how CommitTransactionCommand() leaves it. The callers both think
they are using short-lived contexts, for th
Prevent long-term memory leakage in autovacuum launcher.
get_database_list() failed to restore the caller's memory context,
instead leaving current context set to TopMemoryContext which is
how CommitTransactionCommand() leaves it. The callers both think
they are using short-lived contexts, for th
Prevent long-term memory leakage in autovacuum launcher.
get_database_list() failed to restore the caller's memory context,
instead leaving current context set to TopMemoryContext which is
how CommitTransactionCommand() leaves it. The callers both think
they are using short-lived contexts, for th
Prevent long-term memory leakage in autovacuum launcher.
get_database_list() failed to restore the caller's memory context,
instead leaving current context set to TopMemoryContext which is
how CommitTransactionCommand() leaves it. The callers both think
they are using short-lived contexts, for th
doc: simplify WITH clause syntax in CREATE DATABASE
Reported-by: Rob
Discussion: https://postgr.es/m/20211016171149.yaouvlw5kvux6dvk@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/6a6edc0c8b5f09ce77d0c3940252
doc: simplify WITH clause syntax in CREATE DATABASE
Reported-by: Rob
Discussion: https://postgr.es/m/20211016171149.yaouvlw5kvux6dvk@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d07eecdce3d7b56f40405ad15f83
doc: simplify WITH clause syntax in CREATE DATABASE
Reported-by: Rob
Discussion: https://postgr.es/m/20211016171149.yaouvlw5kvux6dvk@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/3da5ecb98c80be0a5c8064b7e4b8
doc: simplify WITH clause syntax in CREATE DATABASE
Reported-by: Rob
Discussion: https://postgr.es/m/20211016171149.yaouvlw5kvux6dvk@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/ba018102466f3bcd12f131ac6c91
doc: simplify WITH clause syntax in CREATE DATABASE
Reported-by: Rob
Discussion: https://postgr.es/m/20211016171149.yaouvlw5kvux6dvk@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/cdb836cc2d04b6eee4f14e2f1292
doc: simplify WITH clause syntax in CREATE DATABASE
Reported-by: Rob
Discussion: https://postgr.es/m/20211016171149.yaouvlw5kvux6dvk@localhost
Author: Rob
Backpatch-through: 10
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/349baa87ae4bf1c65c3ed34073837a71a72
doc: simplify WITH clause syntax in CREATE DATABASE
Reported-by: Rob
Discussion: https://postgr.es/m/20211016171149.yaouvlw5kvux6dvk@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/c1f54eac3ab67e70f507cd82d405
Be smarter about freeing tuples during tuplesorts
During dumptuples() the call to writetuple() would pfree any non-null
tuple. This was quite wasteful as this happens just before we perform a
reset of the context which stores all of those tuples.
It seems to make sense to do a bit of a code refa
doc: show direction is optional in FETCH/MOVE's FROM/IN syntax
It used to show direction was required for FROM/IN.
Reported-by: Rob
Discussion: https://postgr.es/m/20211015165248.isqjceyilelhnu3k@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
---
https
doc: show direction is optional in FETCH/MOVE's FROM/IN syntax
It used to show direction was required for FROM/IN.
Reported-by: Rob
Discussion: https://postgr.es/m/20211015165248.isqjceyilelhnu3k@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
---
https
doc: show direction is optional in FETCH/MOVE's FROM/IN syntax
It used to show direction was required for FROM/IN.
Reported-by: Rob
Discussion: https://postgr.es/m/20211015165248.isqjceyilelhnu3k@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
---
https
doc: show direction is optional in FETCH/MOVE's FROM/IN syntax
It used to show direction was required for FROM/IN.
Reported-by: Rob
Discussion: https://postgr.es/m/20211015165248.isqjceyilelhnu3k@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
---
https
doc: show direction is optional in FETCH/MOVE's FROM/IN syntax
It used to show direction was required for FROM/IN.
Reported-by: Rob
Discussion: https://postgr.es/m/20211015165248.isqjceyilelhnu3k@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https
doc: show direction is optional in FETCH/MOVE's FROM/IN syntax
It used to show direction was required for FROM/IN.
Reported-by: Rob
Discussion: https://postgr.es/m/20211015165248.isqjceyilelhnu3k@localhost
Author: Rob
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
---
https
doc: show direction is optional in FETCH/MOVE's FROM/IN syntax
It used to show direction was required for FROM/IN.
Reported-by: Rob
Discussion: https://postgr.es/m/20211015165248.isqjceyilelhnu3k@localhost
Author: Rob
Backpatch-through: 10
Branch
--
master
Details
---
https://git.
doc: document the maximum char/varchar length value
Reported-by: Japin Li
Discussion:
https://postgr.es/m/meyp282mb1669b13e98ae531617cb1386b6...@meyp282mb1669.ausp282.prod.outlook.com
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/c
doc: document the maximum char/varchar length value
Reported-by: Japin Li
Discussion:
https://postgr.es/m/meyp282mb1669b13e98ae531617cb1386b6...@meyp282mb1669.ausp282.prod.outlook.com
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/7
doc: document the maximum char/varchar length value
Reported-by: Japin Li
Discussion:
https://postgr.es/m/meyp282mb1669b13e98ae531617cb1386b6...@meyp282mb1669.ausp282.prod.outlook.com
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/e
doc: document the maximum char/varchar length value
Reported-by: Japin Li
Discussion:
https://postgr.es/m/meyp282mb1669b13e98ae531617cb1386b6...@meyp282mb1669.ausp282.prod.outlook.com
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9
doc: document the maximum char/varchar length value
Reported-by: Japin Li
Discussion:
https://postgr.es/m/meyp282mb1669b13e98ae531617cb1386b6...@meyp282mb1669.ausp282.prod.outlook.com
Backpatch-through: 10
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/62c49fca
doc: document the maximum char/varchar length value
Reported-by: Japin Li
Discussion:
https://postgr.es/m/meyp282mb1669b13e98ae531617cb1386b6...@meyp282mb1669.ausp282.prod.outlook.com
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/3
doc: document the maximum char/varchar length value
Reported-by: Japin Li
Discussion:
https://postgr.es/m/meyp282mb1669b13e98ae531617cb1386b6...@meyp282mb1669.ausp282.prod.outlook.com
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/e
doc: mention that SET TIME ZONE often needs to be quoted
Also mention that time zone abbreviations are not supported.
Reported-by: philippe.godf...@nov.com
Discussion:
https://postgr.es/m/163888728952.1269.5167822676466793...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_15
doc: mention that SET TIME ZONE often needs to be quoted
Also mention that time zone abbreviations are not supported.
Reported-by: philippe.godf...@nov.com
Discussion:
https://postgr.es/m/163888728952.1269.5167822676466793...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_14
doc: mention that SET TIME ZONE often needs to be quoted
Also mention that time zone abbreviations are not supported.
Reported-by: philippe.godf...@nov.com
Discussion:
https://postgr.es/m/163888728952.1269.5167822676466793...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_10
doc: mention that SET TIME ZONE often needs to be quoted
Also mention that time zone abbreviations are not supported.
Reported-by: philippe.godf...@nov.com
Discussion:
https://postgr.es/m/163888728952.1269.5167822676466793...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_12
doc: mention that SET TIME ZONE often needs to be quoted
Also mention that time zone abbreviations are not supported.
Reported-by: philippe.godf...@nov.com
Discussion:
https://postgr.es/m/163888728952.1269.5167822676466793...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_13
doc: mention that SET TIME ZONE often needs to be quoted
Also mention that time zone abbreviations are not supported.
Reported-by: philippe.godf...@nov.com
Discussion:
https://postgr.es/m/163888728952.1269.5167822676466793...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_11
doc: mention that SET TIME ZONE often needs to be quoted
Also mention that time zone abbreviations are not supported.
Reported-by: philippe.godf...@nov.com
Discussion:
https://postgr.es/m/163888728952.1269.5167822676466793...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
master
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
Non-sql_body functions are evaluated at runtime.
Reported-by: Erki Eessaar
Discussion:
https://postgr.es/m/am9pr01mb8268bf5e74e119828251fd34fe...@am9pr01mb8268.eurprd01.prod.exchangelabs.com
Backpatch-through: 10
Branch
--
R
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
Non-sql_body functions are evaluated at runtime.
Reported-by: Erki Eessaar
Discussion:
https://postgr.es/m/am9pr01mb8268bf5e74e119828251fd34fe...@am9pr01mb8268.eurprd01.prod.exchangelabs.com
Backpatch-through: 10
Branch
--
R
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
Non-sql_body functions are evaluated at runtime.
Reported-by: Erki Eessaar
Discussion:
https://postgr.es/m/am9pr01mb8268bf5e74e119828251fd34fe...@am9pr01mb8268.eurprd01.prod.exchangelabs.com
Backpatch-through: 10
Branch
--
m
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
Non-sql_body functions are evaluated at runtime.
Reported-by: Erki Eessaar
Discussion:
https://postgr.es/m/am9pr01mb8268bf5e74e119828251fd34fe...@am9pr01mb8268.eurprd01.prod.exchangelabs.com
Backpatch-through: 10
Branch
--
R
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
Non-sql_body functions are evaluated at runtime.
Reported-by: Erki Eessaar
Discussion:
https://postgr.es/m/am9pr01mb8268bf5e74e119828251fd34fe...@am9pr01mb8268.eurprd01.prod.exchangelabs.com
Backpatch-through: 10
Branch
--
R
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
Non-sql_body functions are evaluated at runtime.
Reported-by: Erki Eessaar
Discussion:
https://postgr.es/m/am9pr01mb8268bf5e74e119828251fd34fe...@am9pr01mb8268.eurprd01.prod.exchangelabs.com
Backpatch-through: 10
Branch
--
R
doc: warn of SECURITY DEFINER schemas for non-sql_body functions
Non-sql_body functions are evaluated at runtime.
Reported-by: Erki Eessaar
Discussion:
https://postgr.es/m/am9pr01mb8268bf5e74e119828251fd34fe...@am9pr01mb8268.eurprd01.prod.exchangelabs.com
Backpatch-through: 10
Branch
--
R
Port regress-python3-mangle.mk to Solaris "sed", redux.
Per experimentation and buildfarm failures, Solaris' "sed"
has got some kind of problem with regexes that use both '*'
and '[[:alpha:]]'. We can work around that by replacing
'[[:alpha:]]' with '[a-zA-Z]', which is plenty good enough
for our
Port regress-python3-mangle.mk to Solaris "sed", redux.
Per experimentation and buildfarm failures, Solaris' "sed"
has got some kind of problem with regexes that use both '*'
and '[[:alpha:]]'. We can work around that by replacing
'[[:alpha:]]' with '[a-zA-Z]', which is plenty good enough
for our
Port regress-python3-mangle.mk to Solaris "sed", redux.
Per experimentation and buildfarm failures, Solaris' "sed"
has got some kind of problem with regexes that use both '*'
and '[[:alpha:]]'. We can work around that by replacing
'[[:alpha:]]' with '[a-zA-Z]', which is plenty good enough
for our
doc: split out the NATURAL/CROSS JOIN in SELECT syntax
This allows the syntax to be more accurate about what clauses are
supported. Also switch an example query to use the ANSI join syntax.
Reported-by: Joel Jacobson
Discussion:
https://postgr.es/m/67b71d3e-0c22-44df-a223-351f14418...@www.fas
doc: split out the NATURAL/CROSS JOIN in SELECT syntax
This allows the syntax to be more accurate about what clauses are
supported. Also switch an example query to use the ANSI join syntax.
Reported-by: Joel Jacobson
Discussion:
https://postgr.es/m/67b71d3e-0c22-44df-a223-351f14418...@www.fas
doc: split out the NATURAL/CROSS JOIN in SELECT syntax
This allows the syntax to be more accurate about what clauses are
supported. Also switch an example query to use the ANSI join syntax.
Reported-by: Joel Jacobson
Discussion:
https://postgr.es/m/67b71d3e-0c22-44df-a223-351f14418...@www.fas
doc: split out the NATURAL/CROSS JOIN in SELECT syntax
This allows the syntax to be more accurate about what clauses are
supported. Also switch an example query to use the ANSI join syntax.
Reported-by: Joel Jacobson
Discussion:
https://postgr.es/m/67b71d3e-0c22-44df-a223-351f14418...@www.fas
doc: split out the NATURAL/CROSS JOIN in SELECT syntax
This allows the syntax to be more accurate about what clauses are
supported. Also switch an example query to use the ANSI join syntax.
Reported-by: Joel Jacobson
Discussion:
https://postgr.es/m/67b71d3e-0c22-44df-a223-351f14418...@www.fas
doc: split out the NATURAL/CROSS JOIN in SELECT syntax
This allows the syntax to be more accurate about what clauses are
supported. Also switch an example query to use the ANSI join syntax.
Reported-by: Joel Jacobson
Discussion:
https://postgr.es/m/67b71d3e-0c22-44df-a223-351f14418...@www.fas
doc: clarify that pgcrypto's gen_random_uuid calls core func.
Previously it was just marked as a duplicate of the core function.
Reported-by: Andreas Dijkman
Discussion: https://postgr.es/m/17349-24d61e214429e...@postgresql.org
Backpatch-through: 13
Branch
--
REL_13_STABLE
Details
--
doc: clarify that pgcrypto's gen_random_uuid calls core func.
Previously it was just marked as a duplicate of the core function.
Reported-by: Andreas Dijkman
Discussion: https://postgr.es/m/17349-24d61e214429e...@postgresql.org
Backpatch-through: 13
Branch
--
REL_15_STABLE
Details
--
doc: clarify that pgcrypto's gen_random_uuid calls core func.
Previously it was just marked as a duplicate of the core function.
Reported-by: Andreas Dijkman
Discussion: https://postgr.es/m/17349-24d61e214429e...@postgresql.org
Backpatch-through: 13
Branch
--
master
Details
---
https
doc: clarify that pgcrypto's gen_random_uuid calls core func.
Previously it was just marked as a duplicate of the core function.
Reported-by: Andreas Dijkman
Discussion: https://postgr.es/m/17349-24d61e214429e...@postgresql.org
Backpatch-through: 13
Branch
--
REL_14_STABLE
Details
--
doc: use FILTER in aggregate example
Reported-by: michal.pale...@freemap.sk
Discussion:
https://postgr.es/m/163499710897.684.7420075366995883...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d333a1a16240b629
doc: use FILTER in aggregate example
Reported-by: michal.pale...@freemap.sk
Discussion:
https://postgr.es/m/163499710897.684.7420075366995883...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d11a53a8e0a77c95
doc: use FILTER in aggregate example
Reported-by: michal.pale...@freemap.sk
Discussion:
https://postgr.es/m/163499710897.684.7420075366995883...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/6a27e2f5339479de
doc: use FILTER in aggregate example
Reported-by: michal.pale...@freemap.sk
Discussion:
https://postgr.es/m/163499710897.684.7420075366995883...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/fede15417225c08479fc6cd
doc: use FILTER in aggregate example
Reported-by: michal.pale...@freemap.sk
Discussion:
https://postgr.es/m/163499710897.684.7420075366995883...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/d55fdfb554348ffd
doc: use FILTER in aggregate example
Reported-by: michal.pale...@freemap.sk
Discussion:
https://postgr.es/m/163499710897.684.7420075366995883...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/994667f899c70c66
doc: use FILTER in aggregate example
Reported-by: michal.pale...@freemap.sk
Discussion:
https://postgr.es/m/163499710897.684.7420075366995883...@wrigleys.postgresql.org
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/de73544bb46dc141
Adjust XML test case to avoid unstable behavior.
Buildfarm member bowerbird is (inconsistently) showing different
results for this test case since we enabled ASLR for MSVC builds.
It's not very clear whether that's a bug in its version of libxml2
or the test case is relying on nominally-undefined
doc: mention "bloom" as a possible index access method
Also remove USING erroneously added recently.
Reported-by: Jeff Janes
Discussion:
https://postgr.es/m/CAMkU=1zhcpc7hottymwm5pimr9vrlprswzlg+7pgajwhkzq...@mail.gmail.com
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
---
ht
doc: mention "bloom" as a possible index access method
Also remove USING erroneously added recently.
Reported-by: Jeff Janes
Discussion:
https://postgr.es/m/CAMkU=1zhcpc7hottymwm5pimr9vrlprswzlg+7pgajwhkzq...@mail.gmail.com
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
---
ht
doc: mention "bloom" as a possible index access method
Also remove USING erroneously added recently.
Reported-by: Jeff Janes
Discussion:
https://postgr.es/m/CAMkU=1zhcpc7hottymwm5pimr9vrlprswzlg+7pgajwhkzq...@mail.gmail.com
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
---
ht
doc: mention "bloom" as a possible index access method
Also remove USING erroneously added recently.
Reported-by: Jeff Janes
Discussion:
https://postgr.es/m/CAMkU=1zhcpc7hottymwm5pimr9vrlprswzlg+7pgajwhkzq...@mail.gmail.com
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
---
ht
doc: mention "bloom" as a possible index access method
Also remove USING erroneously added recently.
Reported-by: Jeff Janes
Discussion:
https://postgr.es/m/CAMkU=1zhcpc7hottymwm5pimr9vrlprswzlg+7pgajwhkzq...@mail.gmail.com
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
---
ht
doc: mention "bloom" as a possible index access method
Also remove USING erroneously added recently.
Reported-by: Jeff Janes
Discussion:
https://postgr.es/m/CAMkU=1zhcpc7hottymwm5pimr9vrlprswzlg+7pgajwhkzq...@mail.gmail.com
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
ht
doc: mention "bloom" as a possible index access method
Also remove USING erroneously added recently.
Reported-by: Jeff Janes
Discussion:
https://postgr.es/m/CAMkU=1zhcpc7hottymwm5pimr9vrlprswzlg+7pgajwhkzq...@mail.gmail.com
Backpatch-through: 10
Branch
--
master
Details
---
https://g
doc: in create statistics docs, mention analyze for parent info
Discussion: https://postgr.es/m/yv1bw8j+1pyfh...@momjian.us
Backpatch-through: 10
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/974299a808554a0983e92923a06e14e899cb2b55
Modified Files
--
doc: in create statistics docs, mention analyze for parent info
Discussion: https://postgr.es/m/yv1bw8j+1pyfh...@momjian.us
Backpatch-through: 10
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/8f32ac5a16197f1ee89c6b20be9ea209dc5da5ee
Modified Files
--
doc: in create statistics docs, mention analyze for parent info
Discussion: https://postgr.es/m/yv1bw8j+1pyfh...@momjian.us
Backpatch-through: 10
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/5be9cffa9d83cee569d77286a5136ad27855f05a
Modified Files
--
doc: in create statistics docs, mention analyze for parent info
Discussion: https://postgr.es/m/yv1bw8j+1pyfh...@momjian.us
Backpatch-through: 10
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/35221314923ea3303504f8bad440e8efbd687968
Modified Files
--
doc: in create statistics docs, mention analyze for parent info
Discussion: https://postgr.es/m/yv1bw8j+1pyfh...@momjian.us
Backpatch-through: 10
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/97fe6d2210d4c6a0be3ff16abc9432b2c0a867b8
Modified Files
-
doc: in create statistics docs, mention analyze for parent info
Discussion: https://postgr.es/m/yv1bw8j+1pyfh...@momjian.us
Backpatch-through: 10
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/f988e94f51ab4fef6e264c6799168ef4551f66b1
Modified Files
--
doc: in create statistics docs, mention analyze for parent info
Discussion: https://postgr.es/m/yv1bw8j+1pyfh...@momjian.us
Backpatch-through: 10
Branch
--
REL_12_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/dc565a4597e9412a731960a4df092637e7a833c7
Modified Files
--
90 matches
Mail list logo
