public inbox for [email protected]  

help / color / mirror / Atom feed

[PATCH v6] Highlight vacuum consideration in create index docs
24+ messages / 3 participants
[nested] [flat]

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* [PATCH v6] Highlight vacuum consideration in create index docs
@ 2020-11-30 21:50  Alvaro Herrera <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Alvaro Herrera @ 2020-11-30 21:50 UTC (permalink / raw)

Per James Coleman
---
 doc/src/sgml/ref/create_index.sgml | 5 +++++
 doc/src/sgml/ref/reindex.sgml      | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2054d5d943..d951f14b09 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -829,6 +829,11 @@ Indexes:
    to remove an index.
   </para>
 
+  <para>
+   Like any long-running transaction, <command>CREATE INDEX</command> can
+   affect which tuples can be removed by concurrent <command>VACUUM</command>.
+  </para>
+
   <para>
    Prior releases of <productname>PostgreSQL</productname> also had an
    R-tree index method.  This method has been removed because
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf06713..ef553f6481 100644
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,11 @@ Indexes:
     CONCURRENTLY</command> cannot.
    </para>
 
+   <para>
+    Like any long-running transaction, <command>REINDEX</command> can
+    affect which tuples can be removed by concurrent <command>VACUUM</command>.
+   </para>
+
    <para>
     <command>REINDEX SYSTEM</command> does not support
     <command>CONCURRENTLY</command> since system catalogs cannot be reindexed
-- 
2.20.1


--+QahgC5+KEYLbs62--





^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: Scan buffercache for a table
@ 2023-01-31 02:43  Justin Pryzby <[email protected]>
  0 siblings, 1 reply; 24+ messages in thread

From: Justin Pryzby @ 2023-01-31 02:43 UTC (permalink / raw)
  To: Amin <[email protected]>; +Cc: pgsql-hackers

On Mon, Jan 30, 2023 at 06:01:08PM -0800, Amin wrote:
> Hi,
> 
> I am looking for function calls to scan the buffer cache for a table and
> find the cached pages. I want to find out which pages are cached and which
> of them are dirty. Having the relation id, how can I do that? I have gone
> through bufmgr.c and relcache.c, but could not find a way to get
> relation-specific pages from the buffer cache.

This looks like a re-post of the question you asked on Jan 13:
CAF-KA8_axSMpQW1scOTnAQx8NFHgmJc6L87QzAo3JezLiBU1HQ@mail.gmail.com
It'd be better not to start a new thread (or if you do that, it'd be
better to mention the old one and include its participants).

On Fri, Jan 13, 2023 at 05:28:31PM -0800, Amin wrote:
> Hi,
> 
> Before scanning a relation, in the planner stage, I want to make a
> call to
> retrieve information about how many pages will be a hit for a specific
> relation. The module pg_buffercache seems to be doing a similar thing.

The planner is a *model* which (among other things) tries to guess how
many pages will be read/hit.  It's not expected to be anywhere near
accurate.

pg_buffercache only checks for pages within postgres' own buffer cache.
It doesn't look for pages which are in the OS page cache, which require
a system call to access (but don't require device I/O).

Read about pgfincore for introinspection of the OS page cache.

> Also, pg_statio_all_tables seems to be having that information, but it
> is updated after execution. However, I want the information before
> execution.  Also not sure how pg_statio_all_tables is created and how
> I can access it in the code.

But the view isn't omnicient.  When you execute a plan, you don't know
how it's going to end.  If you did, you wouldn't need to run it - you
could just print the answer.

Note that planning and execution are separate and independant.  It's
possible to plan a query without ever running it, or to plan it once and
run it multiple times.  The view reflects I/O requested by postgres; the
I/O normally comes primarily from execution.

You can look at how the view is defined:
\sv pg_statio_all_tables

And then you can look at how the functions that it calls are implemented
(\df+).  Same for pg_buffercache.  It seems like you'll want to learn
how to navigate the source code to find how things are connected.

-- 
Justin






^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: Scan buffercache for a table
@ 2023-01-31 04:11  Amin <[email protected]>
  parent: Justin Pryzby <[email protected]>
  0 siblings, 1 reply; 24+ messages in thread

From: Amin @ 2023-01-31 04:11 UTC (permalink / raw)
  To: Justin Pryzby <[email protected]>; +Cc: pgsql-hackers

Thank you Justin. I started a new thread because the context is a little
bit different. I am no longer interested in statistics anymore. I want to
find exact individual pages of a table which are cached and are/aren't
dirty. pg_buffercache implements the loop, but it goes over all the
buffers. However, I want to scan a specific table cache pages.

On Mon, Jan 30, 2023 at 6:43 PM Justin Pryzby <[email protected]> wrote:

> On Mon, Jan 30, 2023 at 06:01:08PM -0800, Amin wrote:
> > Hi,
> >
> > I am looking for function calls to scan the buffer cache for a table and
> > find the cached pages. I want to find out which pages are cached and
> which
> > of them are dirty. Having the relation id, how can I do that? I have gone
> > through bufmgr.c and relcache.c, but could not find a way to get
> > relation-specific pages from the buffer cache.
>
> This looks like a re-post of the question you asked on Jan 13:
> CAF-KA8_axSMpQW1scOTnAQx8NFHgmJc6L87QzAo3JezLiBU1HQ@mail.gmail.com
> It'd be better not to start a new thread (or if you do that, it'd be
> better to mention the old one and include its participants).
>
> On Fri, Jan 13, 2023 at 05:28:31PM -0800, Amin wrote:
> > Hi,
> >
> > Before scanning a relation, in the planner stage, I want to make a
> > call to
> > retrieve information about how many pages will be a hit for a specific
> > relation. The module pg_buffercache seems to be doing a similar thing.
>
> The planner is a *model* which (among other things) tries to guess how
> many pages will be read/hit.  It's not expected to be anywhere near
> accurate.
>
> pg_buffercache only checks for pages within postgres' own buffer cache.
> It doesn't look for pages which are in the OS page cache, which require
> a system call to access (but don't require device I/O).
>
> Read about pgfincore for introinspection of the OS page cache.
>
> > Also, pg_statio_all_tables seems to be having that information, but it
> > is updated after execution. However, I want the information before
> > execution.  Also not sure how pg_statio_all_tables is created and how
> > I can access it in the code.
>
> But the view isn't omnicient.  When you execute a plan, you don't know
> how it's going to end.  If you did, you wouldn't need to run it - you
> could just print the answer.
>
> Note that planning and execution are separate and independant.  It's
> possible to plan a query without ever running it, or to plan it once and
> run it multiple times.  The view reflects I/O requested by postgres; the
> I/O normally comes primarily from execution.
>
> You can look at how the view is defined:
> \sv pg_statio_all_tables
>
> And then you can look at how the functions that it calls are implemented
> (\df+).  Same for pg_buffercache.  It seems like you'll want to learn
> how to navigate the source code to find how things are connected.
>
> --
> Justin
>


^ permalink  raw  reply  [nested|flat] 24+ messages in thread

* Re: Scan buffercache for a table
@ 2023-01-31 13:11  Justin Pryzby <[email protected]>
  parent: Amin <[email protected]>
  0 siblings, 0 replies; 24+ messages in thread

From: Justin Pryzby @ 2023-01-31 13:11 UTC (permalink / raw)
  To: Amin <[email protected]>; +Cc: pgsql-hackers

On Mon, Jan 30, 2023 at 08:11:30PM -0800, Amin wrote:
> Thank you Justin. I started a new thread because the context is a little
> bit different. I am no longer interested in statistics anymore. I want to
> find exact individual pages of a table which are cached and are/aren't
> dirty. pg_buffercache implements the loop, but it goes over all the
> buffers. However, I want to scan a specific table cache pages.

Check ReadBuffer*(), BufTableLookup() or loops around it like
FindAndDropRelationBuffers(), which is in the file you referenced.

> > On Mon, Jan 30, 2023 at 06:01:08PM -0800, Amin wrote:
> > > Hi,
> > >
> > > I am looking for function calls to scan the buffer cache for a table and
> > > find the cached pages. I want to find out which pages are cached and which
> > > of them are dirty. Having the relation id, how can I do that? I have gone
> > > through bufmgr.c and relcache.c, but could not find a way to get
> > > relation-specific pages from the buffer cache.






^ permalink  raw  reply  [nested|flat] 24+ messages in thread

end of thread, other threads:[~2023-01-31 13:11 UTC | newest]

Thread overview: 24+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2020-11-30 21:50 [PATCH v6] Highlight vacuum consideration in create index docs Alvaro Herrera <[email protected]>
2023-01-31 02:43 Re: Scan buffercache for a table Justin Pryzby <[email protected]>
2023-01-31 04:11 ` Re: Scan buffercache for a table Amin <[email protected]>
2023-01-31 13:11   ` Re: Scan buffercache for a table Justin Pryzby <[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