public inbox for [email protected]
help / color / mirror / Atom feedMissing SIZE_MAX
51+ messages / 6 participants
[nested] [flat]
* Missing SIZE_MAX
@ 2017-09-01 15:09 Tom Lane <[email protected]>
2017-09-01 15:48 ` Re: Missing SIZE_MAX Robert Haas <[email protected]>
2017-09-01 15:50 ` Re: Missing SIZE_MAX Alvaro Herrera <[email protected]>
0 siblings, 2 replies; 51+ messages in thread
From: Tom Lane @ 2017-09-01 15:09 UTC (permalink / raw)
To: pgsql-hackers
Commit 2e70d6b5e added a dependency on SIZE_MAX to libpq/fe_exec.c.
According to C99 and recent POSIX, that symbol should be provided
by <stdint.h>, but SUS v2 (POSIX 2001) doesn't require <stdint.h>
to exist at all ... and I now notice that gaur/pademelon doesn't
have it, and unsurprisingly is failing to compile fe_exec.c.
We have a workaround for that symbol in timezone/private.h:
#ifndef SIZE_MAX
#define SIZE_MAX ((size_t) -1)
#endif
and a bit of grepping finds other places that are using the (size_t) -1
trick explicitly. So what I'm tempted to do is move the above stanza
into c.h. Any objections?
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
^ permalink raw reply [nested|flat] 51+ messages in thread
* Re: Missing SIZE_MAX
2017-09-01 15:09 Missing SIZE_MAX Tom Lane <[email protected]>
@ 2017-09-01 15:48 ` Robert Haas <[email protected]>
1 sibling, 0 replies; 51+ messages in thread
From: Robert Haas @ 2017-09-01 15:48 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: pgsql-hackers
On Fri, Sep 1, 2017 at 11:09 AM, Tom Lane <[email protected]> wrote:
> Commit 2e70d6b5e added a dependency on SIZE_MAX to libpq/fe_exec.c.
> According to C99 and recent POSIX, that symbol should be provided
> by <stdint.h>, but SUS v2 (POSIX 2001) doesn't require <stdint.h>
> to exist at all ... and I now notice that gaur/pademelon doesn't
> have it, and unsurprisingly is failing to compile fe_exec.c.
>
> We have a workaround for that symbol in timezone/private.h:
>
> #ifndef SIZE_MAX
> #define SIZE_MAX ((size_t) -1)
> #endif
>
> and a bit of grepping finds other places that are using the (size_t) -1
> trick explicitly. So what I'm tempted to do is move the above stanza
> into c.h. Any objections?
Not from me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
^ permalink raw reply [nested|flat] 51+ messages in thread
* Re: Missing SIZE_MAX
2017-09-01 15:09 Missing SIZE_MAX Tom Lane <[email protected]>
@ 2017-09-01 15:50 ` Alvaro Herrera <[email protected]>
2017-09-01 16:22 ` Re: Missing SIZE_MAX Tom Lane <[email protected]>
1 sibling, 1 reply; 51+ messages in thread
From: Alvaro Herrera @ 2017-09-01 15:50 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: pgsql-hackers
Tom Lane wrote:
> We have a workaround for that symbol in timezone/private.h:
>
> #ifndef SIZE_MAX
> #define SIZE_MAX ((size_t) -1)
> #endif
>
> and a bit of grepping finds other places that are using the (size_t) -1
> trick explicitly. So what I'm tempted to do is move the above stanza
> into c.h.
Sounds good to me.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
^ permalink raw reply [nested|flat] 51+ messages in thread
* Re: Missing SIZE_MAX
2017-09-01 15:09 Missing SIZE_MAX Tom Lane <[email protected]>
2017-09-01 15:50 ` Re: Missing SIZE_MAX Alvaro Herrera <[email protected]>
@ 2017-09-01 16:22 ` Tom Lane <[email protected]>
2017-09-01 16:35 ` Re: Missing SIZE_MAX Robert Haas <[email protected]>
0 siblings, 1 reply; 51+ messages in thread
From: Tom Lane @ 2017-09-01 16:22 UTC (permalink / raw)
To: Alvaro Herrera <[email protected]>; +Cc: pgsql-hackers; Robert Haas <[email protected]>
[ warning: more than you really wanted to know ahead ]
Alvaro Herrera <[email protected]> writes:
> Tom Lane wrote:
>> We have a workaround for that symbol in timezone/private.h:
>> #ifndef SIZE_MAX
>> #define SIZE_MAX ((size_t) -1)
>> #endif
>> and a bit of grepping finds other places that are using the (size_t) -1
>> trick explicitly. So what I'm tempted to do is move the above stanza
>> into c.h.
> Sounds good to me.
On closer inspection, C99 requires SIZE_MAX and related macros to be a
"constant expression suitable for use in #if preprocessing directives",
which we need for the fe-exec.c usage because it does
#if INT_MAX >= (SIZE_MAX / 2)
if (newSize > SIZE_MAX / sizeof(PGresAttValue *))
(We could maybe dispense with this #if check, but I feared that doing
so would result in nanny-ish "expression is constant false" warnings
from some compilers on 64-bit platforms.)
Now, that cast doesn't really work in an #if expression. Some language
lawyering leads me to conclude that in #if, a C compiler will interpret
the above value of SIZE_MAX as "((0) -1)", or just signed -1. So
fe-exec.c's test will surely evaluate to true, which seems like a safe
outcome. But you could certainly imagine other cases where you get
incorrect results if SIZE_MAX looks like a signed -1 to an #if-test.
When I look into /usr/include/stdint.h on my Linux box, I find
# if __WORDSIZE == 64
# define SIZE_MAX (18446744073709551615UL)
# else
# define SIZE_MAX (4294967295U)
# endif
so I thought about trying to duplicate that logic. We can certainly test
SIZEOF_SIZE_T == 8 as a substitute for the #if condition. The hard part
is arriving at a portable spelling of "UL", since it would need to be
"ULL" instead on some platforms. We can't make use of our UINT64CONST
macro because that includes a cast. So it seems like if we want to be
100% correct it would need to be something like
#ifndef SIZE_MAX
#if SIZEOF_SIZE_T == 8
#if SIZEOF_LONG == 8
#define SIZE_MAX (18446744073709551615UL)
#else /* assume unsigned long long is what we need */
#define SIZE_MAX (18446744073709551615ULL)
#endif
#else /* 32-bit */
#define SIZE_MAX (4294967295U)
#endif
#endif
That's mighty ugly. Is it worth the trouble, rather than trusting
that the "(size_t) -1" trick will work? Given that we have so few
needs for SIZE_MAX, I'm kind of inclined just to stick with the cast.
I notice BTW that PG_INT64_MIN, PG_INT64_MAX, and PG_UINT64_MAX
all contain casts and thus are equally risky to test in #if-tests.
I see no at-risk code in our tree right now, but someday we might
need to make those look something like the above, too.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
^ permalink raw reply [nested|flat] 51+ messages in thread
* Re: Missing SIZE_MAX
2017-09-01 15:09 Missing SIZE_MAX Tom Lane <[email protected]>
2017-09-01 15:50 ` Re: Missing SIZE_MAX Alvaro Herrera <[email protected]>
2017-09-01 16:22 ` Re: Missing SIZE_MAX Tom Lane <[email protected]>
@ 2017-09-01 16:35 ` Robert Haas <[email protected]>
2017-09-01 16:49 ` Re: Missing SIZE_MAX Tom Lane <[email protected]>
0 siblings, 1 reply; 51+ messages in thread
From: Robert Haas @ 2017-09-01 16:35 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; pgsql-hackers
On Fri, Sep 1, 2017 at 12:22 PM, Tom Lane <[email protected]> wrote:
> [ warning: more than you really wanted to know ahead ]
It might be worth the effort to clean all of this up, just because the
next person who gets bitten by it may not be as smart as you are.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
^ permalink raw reply [nested|flat] 51+ messages in thread
* Re: Missing SIZE_MAX
2017-09-01 15:09 Missing SIZE_MAX Tom Lane <[email protected]>
2017-09-01 15:50 ` Re: Missing SIZE_MAX Alvaro Herrera <[email protected]>
2017-09-01 16:22 ` Re: Missing SIZE_MAX Tom Lane <[email protected]>
2017-09-01 16:35 ` Re: Missing SIZE_MAX Robert Haas <[email protected]>
@ 2017-09-01 16:49 ` Tom Lane <[email protected]>
2017-09-01 18:25 ` Re: Missing SIZE_MAX Tom Lane <[email protected]>
0 siblings, 1 reply; 51+ messages in thread
From: Tom Lane @ 2017-09-01 16:49 UTC (permalink / raw)
To: Robert Haas <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; pgsql-hackers
Robert Haas <[email protected]> writes:
> On Fri, Sep 1, 2017 at 12:22 PM, Tom Lane <[email protected]> wrote:
>> [ warning: more than you really wanted to know ahead ]
> It might be worth the effort to clean all of this up, just because the
> next person who gets bitten by it may not be as smart as you are.
Yeah. I was just thinking that maybe the appropriate investment of
effort is to make [U]INT64CONST smarter, so that it results in a
properly-suffixed constant and doesn't need a cast. Then it'd be a
lot easier to make these other macros be #if-safe.
Or we could just recast the test in fe-exec.c to not use SIZE_MAX.
Checking whether "SIZEOF_SIZE_T == 4" would really have the same
effect, though it's uglier.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
^ permalink raw reply [nested|flat] 51+ messages in thread
* Re: Missing SIZE_MAX
2017-09-01 15:09 Missing SIZE_MAX Tom Lane <[email protected]>
2017-09-01 15:50 ` Re: Missing SIZE_MAX Alvaro Herrera <[email protected]>
2017-09-01 16:22 ` Re: Missing SIZE_MAX Tom Lane <[email protected]>
2017-09-01 16:35 ` Re: Missing SIZE_MAX Robert Haas <[email protected]>
2017-09-01 16:49 ` Re: Missing SIZE_MAX Tom Lane <[email protected]>
@ 2017-09-01 18:25 ` Tom Lane <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Tom Lane @ 2017-09-01 18:25 UTC (permalink / raw)
To: Robert Haas <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; pgsql-hackers
I wrote:
> Robert Haas <[email protected]> writes:
>> It might be worth the effort to clean all of this up, just because the
>> next person who gets bitten by it may not be as smart as you are.
> Yeah. I was just thinking that maybe the appropriate investment of
> effort is to make [U]INT64CONST smarter, so that it results in a
> properly-suffixed constant and doesn't need a cast. Then it'd be a
> lot easier to make these other macros be #if-safe.
Actually, that looks easier than I thought. The current approach to
[U]INT64CONST dates to before we were willing to require the compiler
to have working 64-bit support. I think that now we can just assume
that either an L/UL or LL/ULL suffix will work, as in the attached
draft. (This'd allow dropping configure's HAVE_LL_CONSTANTS probe
entirely, but I didn't do that yet.)
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Attachments:
[text/x-diff] make-INT64CONST-macro-safe-for-#if.patch (2.6K, ../../[email protected]/2-make-INT64CONST-macro-safe-for-%23if.patch)
download | inline diff:
diff --git a/src/include/c.h b/src/include/c.h
index 4f8bbfc..4fb8ef0 100644
*** a/src/include/c.h
--- b/src/include/c.h
*************** typedef long int int64;
*** 288,293 ****
--- 288,295 ----
#ifndef HAVE_UINT64
typedef unsigned long int uint64;
#endif
+ #define INT64CONST(x) (x##L)
+ #define UINT64CONST(x) (x##UL)
#elif defined(HAVE_LONG_LONG_INT_64)
/* We have working support for "long long int", use that */
*************** typedef long long int int64;
*** 297,316 ****
#ifndef HAVE_UINT64
typedef unsigned long long int uint64;
#endif
#else
/* neither HAVE_LONG_INT_64 nor HAVE_LONG_LONG_INT_64 */
#error must have a working 64-bit integer datatype
#endif
- /* Decide if we need to decorate 64-bit constants */
- #ifdef HAVE_LL_CONSTANTS
- #define INT64CONST(x) ((int64) x##LL)
- #define UINT64CONST(x) ((uint64) x##ULL)
- #else
- #define INT64CONST(x) ((int64) x)
- #define UINT64CONST(x) ((uint64) x)
- #endif
-
/* snprintf format strings to use for 64-bit integers */
#define INT64_FORMAT "%" INT64_MODIFIER "d"
#define UINT64_FORMAT "%" INT64_MODIFIER "u"
--- 299,311 ----
#ifndef HAVE_UINT64
typedef unsigned long long int uint64;
#endif
+ #define INT64CONST(x) (x##LL)
+ #define UINT64CONST(x) (x##ULL)
#else
/* neither HAVE_LONG_INT_64 nor HAVE_LONG_LONG_INT_64 */
#error must have a working 64-bit integer datatype
#endif
/* snprintf format strings to use for 64-bit integers */
#define INT64_FORMAT "%" INT64_MODIFIER "d"
#define UINT64_FORMAT "%" INT64_MODIFIER "u"
*************** typedef unsigned PG_INT128_TYPE uint128;
*** 338,351 ****
#define PG_UINT16_MAX (0xFFFF)
#define PG_INT32_MIN (-0x7FFFFFFF-1)
#define PG_INT32_MAX (0x7FFFFFFF)
! #define PG_UINT32_MAX (0xFFFFFFFF)
#define PG_INT64_MIN (-INT64CONST(0x7FFFFFFFFFFFFFFF) - 1)
#define PG_INT64_MAX INT64CONST(0x7FFFFFFFFFFFFFFF)
#define PG_UINT64_MAX UINT64CONST(0xFFFFFFFFFFFFFFFF)
/* Max value of size_t might also be missing if we don't have stdint.h */
#ifndef SIZE_MAX
! #define SIZE_MAX ((size_t) -1)
#endif
/*
--- 333,350 ----
#define PG_UINT16_MAX (0xFFFF)
#define PG_INT32_MIN (-0x7FFFFFFF-1)
#define PG_INT32_MAX (0x7FFFFFFF)
! #define PG_UINT32_MAX (0xFFFFFFFFU)
#define PG_INT64_MIN (-INT64CONST(0x7FFFFFFFFFFFFFFF) - 1)
#define PG_INT64_MAX INT64CONST(0x7FFFFFFFFFFFFFFF)
#define PG_UINT64_MAX UINT64CONST(0xFFFFFFFFFFFFFFFF)
/* Max value of size_t might also be missing if we don't have stdint.h */
#ifndef SIZE_MAX
! #if SIZEOF_SIZE_T == 8
! #define SIZE_MAX PG_UINT64_MAX
! #else
! #define SIZE_MAX PG_UINT32_MAX
! #endif
#endif
/*
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0001-doc-review-COPY-progress-8a4f618e7ae3cb11b0b37d0f06f.patch"
^ permalink raw reply [nested|flat] 51+ messages in thread
* [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f
@ 2021-01-07 01:08 Justin Pryzby <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: Justin Pryzby @ 2021-01-07 01:08 UTC (permalink / raw)
---
doc/src/sgml/monitoring.sgml | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383..3cdb1aff3c 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<para>
Whenever <command>COPY</command> is running, the
<structname>pg_stat_progress_copy</structname> view will contain one row
- for each backend that is currently running <command>COPY</command> command.
- The table bellow describes the information that will be reported and provide
- information how to interpret it.
+ for each backend that is currently running a <command>COPY</command> command.
+ The table below describes the information that will be reported and provides
+ information about how to interpret it.
</para>
<table id="pg-stat-progress-copy-view" xreflabel="pg_stat_progress_copy">
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
<row>
<entry role="catalog_table_entry"><para role="column_definition">
- <structfield>datid</structfield> <type>text</type>
+ <structfield>datid</structfield> <type>oid</type>
</para>
<para>
OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
</para>
<para>
OID of the table on which the <command>COPY</command> command is executed.
- It is set to 0 if <command>SELECT</command> query is provided.
+ It is set to 0 if copying from a <command>SELECT</command> query.
</para></entry>
</row>
--
2.17.0
--aM3YZ0Iwxop3KEKx--
^ permalink raw reply [nested|flat] 51+ messages in thread
* Re: Add mention of execution time memory for enable_partitionwise_* GUCs
@ 2024-07-19 05:24 Ashutosh Bapat <[email protected]>
2024-07-29 05:07 ` Re: Add mention of execution time memory for enable_partitionwise_* GUCs David Rowley <[email protected]>
0 siblings, 1 reply; 51+ messages in thread
From: Ashutosh Bapat @ 2024-07-19 05:24 UTC (permalink / raw)
To: David Rowley <[email protected]>; +Cc: Dimitrios Apostolou <[email protected]>; PostgreSQL Developers <[email protected]>
On Thu, Jul 18, 2024 at 4:24 PM David Rowley <[email protected]> wrote:
>
> On Thu, 18 Jul 2024 at 22:28, Ashutosh Bapat
> <[email protected]> wrote:
> >
> > On Thu, Jul 18, 2024 at 3:33 PM David Rowley <[email protected]> wrote:
> > > hmm? please tell me what word other than "can" best describes
> > > something that is possible to happen but does not always happen under
> > > all circumstances.
> >
> > May I suggest "may"? :) [1], [2], [3].
>
> Is this a wind-up?
>
> If it's not, I disagree that "may" is a better choice. The
> possibility example in your first link says "It may rain tomorrow.
> (possibility)", but that's something someone would only say if there
> was some evidence to support that, e.g. ominous clouds on the horizon
> at dusk, or >0% chance of precipitation on the weather forecast.
> Nobody is going to say that unless there's some supporting evidence.
> For the executor using work_mem * nparts, we've no evidence either.
> It's just a >0% possibility with no supporting evidence.
I am not a native English speaker and might have made a mistake when
interpreting the definitions. Will leave that aside.
>
> > My point is, we need to highlight the role of work_mem. So modify both
> > the descriptions.
>
> I considered writing about work_mem, but felt I wanted to keep it as
> brief as possible and just have some words that might make someone
> think twice. The details in the work_mem documentation should inform
> the reader that work_mem is per executor node. It likely wouldn't
> hurt to have more documentation around which executor node types can
> use a work_mem, which use work_mem * hash_mem_multiplier and which use
> neither. We tend to not write too much about executor nodes in the
> documents, so I'm not proposing that for this patch.
Something I didn't write in my first reply but wanted to discuss was
the intention of adding those GUCs. Sorry for missing it in my first
email. According to [1] these GUCs were added because of increased
memory consumption during planning and time taken to plan the query.
The execution time memory consumption issue was known even back then
but the GUC was not set to default because of that. But your patch
proposes to change the narrative. In the same thread [1], you will
find the discussion about turning the default to ON once we have fixed
planner's memory and time consumption. We have patches addressing
those issues [2] [3]. With your proposed changes we will almost never
have a chance to turn those GUCs ON by default. That seems a rather
sad prospect.
I am fine if we want to mention that the executor may consume a large
amount of memory when these GUCs are turned ON. Users may decide to
turn those OFF if they can not afford to spend that much memory during
execution. But I don't like tying execution time consumption with
default OFF.
[1] https://www.postgresql.org/message-id/[email protected]...
[2] https://www.postgresql.org/message-id/CAExHW5stmOUobE55pMt83r8UxvfCph%2BPvo5dNpdrVCsBgXEzDQ%40mail.g...
[3] https://www.postgresql.org/message-id/flat/CAJ2pMkZNCgoUKSE+_5LthD+KbXKvq6h2hQN8Esxpxd+cxmgomg@mail....
--
Best Wishes,
Ashutosh Bapat
^ permalink raw reply [nested|flat] 51+ messages in thread
* Re: Add mention of execution time memory for enable_partitionwise_* GUCs
2024-07-19 05:24 Re: Add mention of execution time memory for enable_partitionwise_* GUCs Ashutosh Bapat <[email protected]>
@ 2024-07-29 05:07 ` David Rowley <[email protected]>
0 siblings, 0 replies; 51+ messages in thread
From: David Rowley @ 2024-07-29 05:07 UTC (permalink / raw)
To: Ashutosh Bapat <[email protected]>; +Cc: Dimitrios Apostolou <[email protected]>; PostgreSQL Developers <[email protected]>
On Fri, 19 Jul 2024 at 17:24, Ashutosh Bapat
<[email protected]> wrote:
> I am fine if we want to mention that the executor may consume a large
> amount of memory when these GUCs are turned ON. Users may decide to
> turn those OFF if they can not afford to spend that much memory during
> execution. But I don't like tying execution time consumption with
> default OFF.
Would the attached address your concern about the reasons for defaulting to off?
David
Attachments:
[application/octet-stream] partitionwise_docs.patch (2.3K, ../../CAApHDvo3M6Gfi1m8rxcp0nNGZKEJmuJVVt5CiEDKsvi+wX==Ww@mail.gmail.com/2-partitionwise_docs.patch)
download | inline diff:
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 57cd7bb972..8c7a8b8645 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -5567,9 +5567,13 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
joining the matching partitions. Partitionwise join currently applies
only when the join conditions include all the partition keys, which
must be of the same data type and have one-to-one matching sets of
- child partitions. Because partitionwise join planning can use
- significantly more CPU time and memory during planning, the default is
- <literal>off</literal>.
+ child partitions. With this setting enabled, the number of executor
+ nodes whose memory usage is restricted by <varname>work_mem</varname>
+ appearing in the final plan can increase linearly according to the
+ number of partitions being scanned. This can result in a large
+ increase in overall memory consumption during the execution of the
+ query. Query planning also becomes more expensive in terms of memory
+ and CPU. The default value is <literal>off</literal>.
</para>
</listitem>
</varlistentry>
@@ -5587,9 +5591,13 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
tables to be performed separately for each partition. If the
<literal>GROUP BY</literal> clause does not include the partition
keys, only partial aggregation can be performed on a per-partition
- basis, and finalization must be performed later. Because
- partitionwise grouping or aggregation can use significantly more CPU
- time and memory during planning, the default is
+ basis, and finalization must be performed later. With this setting
+ enabled, the number of executor nodes whose memory usage is restricted
+ by <varname>work_mem</varname> appearing in the final plan can
+ increase linearly according to the number of partitions being scanned.
+ This can result in a large increase in overall memory consumption
+ during the execution of the query. Query planning also becomes more
+ expensive in terms of memory and CPU. The default value is
<literal>off</literal>.
</para>
</listitem>
^ permalink raw reply [nested|flat] 51+ messages in thread
end of thread, other threads:[~2024-07-29 05:07 UTC | newest]
Thread overview: 51+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-09-01 15:09 Missing SIZE_MAX Tom Lane <[email protected]>
2017-09-01 15:48 ` Robert Haas <[email protected]>
2017-09-01 15:50 ` Alvaro Herrera <[email protected]>
2017-09-01 16:22 ` Tom Lane <[email protected]>
2017-09-01 16:35 ` Robert Haas <[email protected]>
2017-09-01 16:49 ` Tom Lane <[email protected]>
2017-09-01 18:25 ` Tom Lane <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2021-01-07 01:08 [PATCH] doc review: COPY progress: 8a4f618e7ae3cb11b0b37d0f06f05c8ff905833f Justin Pryzby <[email protected]>
2024-07-19 05:24 Re: Add mention of execution time memory for enable_partitionwise_* GUCs Ashutosh Bapat <[email protected]>
2024-07-29 05:07 ` Re: Add mention of execution time memory for enable_partitionwise_* GUCs David Rowley <[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