agora inbox for [email protected]help / color / mirror / Atom feed
[PATCH 15/21] doc review for multiranges 27+ messages / 4 participants [nested] [flat]
* [PATCH 15/21] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --jI8keyz6grp/JLjh Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* [PATCH 15/18] doc review for multiranges @ 2021-01-24 03:02 Justin Pryzby <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Justin Pryzby @ 2021-01-24 03:02 UTC (permalink / raw) 6df7a9698bb036610c1e8c6d375e1be38cb26d5f --- doc/src/sgml/extend.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 6e3d82b85b..ec95b4eb01 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -448,7 +448,7 @@ of <type>anycompatible</type> and <type>anycompatiblenonarray</type> inputs, the array element types of <type>anycompatiblearray</type> inputs, the range subtypes of <type>anycompatiblerange</type> inputs, - and the multirange subtypes of <type>anycompatiablemultirange</type> + and the multirange subtypes of <type>anycompatiblemultirange</type> inputs. If <type>anycompatiblenonarray</type> is present then the common type is required to be a non-array type. Once a common type is identified, arguments in <type>anycompatible</type> -- 2.17.0 --lc9FT7cWel8HagAv Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0016-doc-review-for-logical-decoding-of-prepared-xacts.patch" ^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: Track in pg_replication_slots the reason why slots conflict? @ 2023-12-21 09:40 Andres Freund <[email protected]> 0 siblings, 1 reply; 27+ messages in thread From: Andres Freund @ 2023-12-21 09:40 UTC (permalink / raw) To: Michael Paquier <[email protected]>; +Cc: Postgres hackers <[email protected]>; Bertrand Drouvot <[email protected]> Hi, On 2023-12-21 09:21:04 +0900, Michael Paquier wrote: > While listening at Bertrand's talk about logical decoding on standbys > last week at Prague, I got surprised by the fact that we do not > reflect in the catalogs the reason why a conflict happened for a slot. > There are three of them depending on ReplicationSlotInvalidationCause: > - WAL removed. > - Invalid horizon. > - Insufficient WAL level. It should be extremely rare to hit any of these other than "WAL removed", so I'm not sure it's worth adding interface complexity to show them. > ReplicationSlotCtl holds this information, so couldn't it be useful > for monitoring purposes to know why a slot got invalidated and add a > column to pg_get_replication_slots()? This could just be an extra > text conflicting_reason, defaulting to NULL when there's nothing to > see. Extra columns aren't free from a usability perspective. IFF we do something, I think it should be a single column with a cause. Greetings, Andres Freund ^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: Track in pg_replication_slots the reason why slots conflict? @ 2023-12-21 10:38 shveta malik <[email protected]> parent: Andres Freund <[email protected]> 0 siblings, 1 reply; 27+ messages in thread From: shveta malik @ 2023-12-21 10:38 UTC (permalink / raw) To: Andres Freund <[email protected]>; +Cc: Michael Paquier <[email protected]>; Postgres hackers <[email protected]>; Bertrand Drouvot <[email protected]>; shveta malik <[email protected]> On Thu, Dec 21, 2023 at 3:10 PM Andres Freund <[email protected]> wrote: > > Hi, > > On 2023-12-21 09:21:04 +0900, Michael Paquier wrote: > > While listening at Bertrand's talk about logical decoding on standbys > > last week at Prague, I got surprised by the fact that we do not > > reflect in the catalogs the reason why a conflict happened for a slot. > > There are three of them depending on ReplicationSlotInvalidationCause: > > - WAL removed. > > - Invalid horizon. > > - Insufficient WAL level. > > It should be extremely rare to hit any of these other than "WAL removed", so > I'm not sure it's worth adding interface complexity to show them. > > > > ReplicationSlotCtl holds this information, so couldn't it be useful > > for monitoring purposes to know why a slot got invalidated and add a > > column to pg_get_replication_slots()? This could just be an extra > > text conflicting_reason, defaulting to NULL when there's nothing to > > see. > > Extra columns aren't free from a usability perspective. IFF we do something, I > think it should be a single column with a cause. Thanks for the feedback. But do you mean that we replace existing 'conflicting' column with 'cause' in both the function and view (pg_get_replication_slots() and pg_replication_slots)? Or do you mean that we expose 'cause' from pg_get_replication_slots() and use that to display 'conflicting' in pg_replication_slots view? And if we plan to return/display cause from either function or view, then shall it be enum 'ReplicationSlotInvalidationCause' or description/text corresponding to enum? In the other feature being discussed "Synchronize slots from primary to standby" [1] , there is a requirement to replicate invalidation cause of slot from the primary to standby and thus it is needed in enum form there. And thus there was a suggestion earlier to have the function return enum-value and let the view display it as text/description to the user. So kindly let us know your thoughts. [1] - https://www.postgresql.org/message-id/[email protected] thanks Shveta ^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: Track in pg_replication_slots the reason why slots conflict? @ 2023-12-21 11:25 Andres Freund <[email protected]> parent: shveta malik <[email protected]> 0 siblings, 1 reply; 27+ messages in thread From: Andres Freund @ 2023-12-21 11:25 UTC (permalink / raw) To: shveta malik <[email protected]>; +Cc: Michael Paquier <[email protected]>; Postgres hackers <[email protected]>; Bertrand Drouvot <[email protected]> Hi, On 2023-12-21 16:08:48 +0530, shveta malik wrote: > On Thu, Dec 21, 2023 at 3:10 PM Andres Freund <[email protected]> wrote: > > > > Hi, > > > > On 2023-12-21 09:21:04 +0900, Michael Paquier wrote: > > > While listening at Bertrand's talk about logical decoding on standbys > > > last week at Prague, I got surprised by the fact that we do not > > > reflect in the catalogs the reason why a conflict happened for a slot. > > > There are three of them depending on ReplicationSlotInvalidationCause: > > > - WAL removed. > > > - Invalid horizon. > > > - Insufficient WAL level. > > > > It should be extremely rare to hit any of these other than "WAL removed", so > > I'm not sure it's worth adding interface complexity to show them. > > > > > > > ReplicationSlotCtl holds this information, so couldn't it be useful > > > for monitoring purposes to know why a slot got invalidated and add a > > > column to pg_get_replication_slots()? This could just be an extra > > > text conflicting_reason, defaulting to NULL when there's nothing to > > > see. > > > > Extra columns aren't free from a usability perspective. IFF we do something, I > > think it should be a single column with a cause. > > Thanks for the feedback. But do you mean that we replace existing > 'conflicting' column with 'cause' in both the function and view > (pg_get_replication_slots() and pg_replication_slots)? Or do you mean > that we expose 'cause' from pg_get_replication_slots() and use that to > display 'conflicting' in pg_replication_slots view? I'm not entirely sure I understand the difference - just whether we add one new column or replace the existing 'conflicting' column? I can see arguments for either. A conflicting column where NULL indicates no conflict, and other values indicate the reason for the conflict, doesn't seem too bad. > And if we plan to return/display cause from either function or view, > then shall it be enum 'ReplicationSlotInvalidationCause' or > description/text corresponding to enum? We clearly can't just expose the numerical value for a C enum. So it has to be converted to something SQL representable. > In the other feature being discussed "Synchronize slots from primary > to standby" [1] , there is a requirement to replicate invalidation > cause of slot from the primary to standby and thus it is needed in > enum form there. And thus there was a suggestion earlier to have the > function return enum-value and let the view display it as > text/description to the user. So kindly let us know your thoughts. > > [1] - https://www.postgresql.org/message-id/[email protected] Can you point me to a more specific message for that requirement? It seems pretty odd to me. Your link goes to the top of a 400 message thread, I don't have time to find one specific design point in that... Greetings, Andres ^ permalink raw reply [nested|flat] 27+ messages in thread
* Re: Track in pg_replication_slots the reason why slots conflict? @ 2023-12-21 14:25 Amit Kapila <[email protected]> parent: Andres Freund <[email protected]> 0 siblings, 0 replies; 27+ messages in thread From: Amit Kapila @ 2023-12-21 14:25 UTC (permalink / raw) To: Andres Freund <[email protected]>; +Cc: shveta malik <[email protected]>; Michael Paquier <[email protected]>; Postgres hackers <[email protected]>; Bertrand Drouvot <[email protected]> On Thu, Dec 21, 2023 at 5:05 PM Andres Freund <[email protected]> wrote: > > On 2023-12-21 16:08:48 +0530, shveta malik wrote: > > On Thu, Dec 21, 2023 at 3:10 PM Andres Freund <[email protected]> wrote: > > > > > > Extra columns aren't free from a usability perspective. IFF we do something, I > > > think it should be a single column with a cause. > > > > Thanks for the feedback. But do you mean that we replace existing > > 'conflicting' column with 'cause' in both the function and view > > (pg_get_replication_slots() and pg_replication_slots)? Or do you mean > > that we expose 'cause' from pg_get_replication_slots() and use that to > > display 'conflicting' in pg_replication_slots view? > > I'm not entirely sure I understand the difference - just whether we add one > new column or replace the existing 'conflicting' column? I can see arguments > for either. > Agreed. I think the argument against replacing the existing 'conflicting' column is that there is a chance that it is being used by some monitoring script which I guess shouldn't be a big deal to change. So, if we don't see that as a problem, I would prefer to have a single column with conflict reason where one of its values indicates there is no conflict. A conflicting column where NULL indicates no conflict, and other > values indicate the reason for the conflict, doesn't seem too bad. > This is fine too. > > > And if we plan to return/display cause from either function or view, > > then shall it be enum 'ReplicationSlotInvalidationCause' or > > description/text corresponding to enum? > > We clearly can't just expose the numerical value for a C enum. So it has to be > converted to something SQL representable. > We can return int2 value from the function pg_get_replication_slots() and then use that to display a string in the view pg_replication_slots. -- With Regards, Amit Kapila. ^ permalink raw reply [nested|flat] 27+ messages in thread
end of thread, other threads:[~2023-12-21 14:25 UTC | newest] Thread overview: 27+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/21] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2021-01-24 03:02 [PATCH 15/18] doc review for multiranges Justin Pryzby <[email protected]> 2023-12-21 09:40 Re: Track in pg_replication_slots the reason why slots conflict? Andres Freund <[email protected]> 2023-12-21 10:38 ` Re: Track in pg_replication_slots the reason why slots conflict? shveta malik <[email protected]> 2023-12-21 11:25 ` Re: Track in pg_replication_slots the reason why slots conflict? Andres Freund <[email protected]> 2023-12-21 14:25 ` Re: Track in pg_replication_slots the reason why slots conflict? Amit Kapila <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox