public inbox for [email protected]
help / color / mirror / Atom feed[PATCH] Disable autovacuum for BRIN test table
23+ messages / 4 participants
[nested] [flat]
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* [PATCH] Disable autovacuum for BRIN test table
@ 2020-08-17 20:20 Alvaro Herrera <[email protected]>
0 siblings, 0 replies; 23+ messages in thread
From: Alvaro Herrera @ 2020-08-17 20:20 UTC (permalink / raw)
This should improve stability in the tests.
Per buildfarm member hyrax (CLOBBER_CACHE_ALWAYS) via Tom Lane.
Discussion: https://postgr.es/m/[email protected]
---
src/test/regress/expected/brin.out | 2 +-
src/test/regress/sql/brin.sql | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/regress/expected/brin.out b/src/test/regress/expected/brin.out
index 0b14c73fc6..18403498df 100644
--- a/src/test/regress/expected/brin.out
+++ b/src/test/regress/expected/brin.out
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
substr(stringu1, 1, 1)::"char",
diff --git a/src/test/regress/sql/brin.sql b/src/test/regress/sql/brin.sql
index 1289e76ecb..d1a82474f3 100644
--- a/src/test/regress/sql/brin.sql
+++ b/src/test/regress/sql/brin.sql
@@ -26,7 +26,7 @@ CREATE TABLE brintest (byteacol bytea,
int4rangecol int4range,
lsncol pg_lsn,
boxcol box
-) WITH (fillfactor=10);
+) WITH (fillfactor=10, autovacuum_enabled=off);
INSERT INTO brintest SELECT
repeat(stringu1, 8)::bytea,
--
2.20.1
--WIyZ46R2i8wDzkSu--
^ permalink raw reply [nested|flat] 23+ messages in thread
* Re: how to gate experimental features (SQL/PGQ)
@ 2026-01-13 17:24 Tom Lane <[email protected]>
2026-01-15 17:05 ` Re: how to gate experimental features (SQL/PGQ) Andrew Dunstan <[email protected]>
0 siblings, 1 reply; 23+ messages in thread
From: Tom Lane @ 2026-01-13 17:24 UTC (permalink / raw)
To: Jacob Champion <[email protected]>; +Cc: Peter Eisentraut <[email protected]>; Andres Freund <[email protected]>; David G. Johnston <[email protected]>; pgsql-hackers; Ashutosh Bapat <[email protected]>; Jelte Fennema-Nio <[email protected]>
Jacob Champion <[email protected]> writes:
> On Tue, Jan 13, 2026 at 7:17 AM Andres Freund <[email protected]> wrote:
>> I don't even know how you could implement 3) realistically. We have zero
>> infrastructure for making e.g. parser, keyword list etc change due to defines
>> compile time.
> Is that an architecturally unsolvable thing, or is it a simple matter
> of programming? Would it be nice to have said infrastructure?
You'd have to throw out flex and bison and build some sort of
extensible parser. That has some attraction to me personally
(I worked on such systems decades ago at HP), but it's fairly
hard to justify the amount of effort that would be needed to
get there. It might well be slower than a flex/bison parser,
and/or have poorer detection of grammar inconsistencies, either
of which would be bad for our usage.
> But overall, I think I'd rather work with an environment where we
> occasionally say "hey, this clearly-labeled experimental feature was
> not baked enough, pull it back now" as opposed to occasionally saying
> "hey, we never got this one feature everyone wants because we'll never
> be practically sure that it's 'right' enough without user testing".
This seems workable for some kinds of features and less so for others.
As an example, forcing initdb post-release seems like a nonstarter
even for "experimental" features, so anything that affects initial
catalog contents is still going to be a problem.
It strikes me that we do have a mechanism that could be used to cope
with catalog changes, which is to package the new catalog objects as
an extension. Then ALTER EXTENSION UPDATE could be used to migrate
from FooBar Draft-2 to Draft-4. But the tricky bit would be to
replace the extension with in-core objects once we decide it's
completely baked. Our previous attempts to do that sort of thing
have been painful. It might be better just to say that you only
get to change experimental catalog entries once a year in major
releases. (Slow progress is still better than no progress.)
regards, tom lane
^ permalink raw reply [nested|flat] 23+ messages in thread
* Re: how to gate experimental features (SQL/PGQ)
2026-01-13 17:24 Re: how to gate experimental features (SQL/PGQ) Tom Lane <[email protected]>
@ 2026-01-15 17:05 ` Andrew Dunstan <[email protected]>
2026-01-15 17:23 ` Re: how to gate experimental features (SQL/PGQ) Andres Freund <[email protected]>
2026-01-15 17:31 ` Re: how to gate experimental features (SQL/PGQ) Tom Lane <[email protected]>
0 siblings, 2 replies; 23+ messages in thread
From: Andrew Dunstan @ 2026-01-15 17:05 UTC (permalink / raw)
To: Tom Lane <[email protected]>; Jacob Champion <[email protected]>; +Cc: Peter Eisentraut <[email protected]>; Andres Freund <[email protected]>; David G. Johnston <[email protected]>; pgsql-hackers; Ashutosh Bapat <[email protected]>; Jelte Fennema-Nio <[email protected]>
On 2026-01-13 Tu 12:24 PM, Tom Lane wrote:
> Jacob Champion<[email protected]> writes:
>> On Tue, Jan 13, 2026 at 7:17 AM Andres Freund<[email protected]> wrote:
>>> I don't even know how you could implement 3) realistically. We have zero
>>> infrastructure for making e.g. parser, keyword list etc change due to defines
>>> compile time.
>> Is that an architecturally unsolvable thing, or is it a simple matter
>> of programming? Would it be nice to have said infrastructure?
> You'd have to throw out flex and bison and build some sort of
> extensible parser. That has some attraction to me personally
> (I worked on such systems decades ago at HP), but it's fairly
> hard to justify the amount of effort that would be needed to
> get there. It might well be slower than a flex/bison parser,
> and/or have poorer detection of grammar inconsistencies, either
> of which would be bad for our usage.
Maybe, but maybe not. ISTR that gcc abandoned use of bison for their C
compiler a long time ago, and that gnat's Ada compiler was hand cut from
the get go.
SQL is a different kettle of fish, of course - it dwarfs C and Ada in
complexity.
Not saying I think this would be a good thing or not. I agree that the
effort required would be huge and the benefit might be modest, but it is
feasible IMHO.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
^ permalink raw reply [nested|flat] 23+ messages in thread
* Re: how to gate experimental features (SQL/PGQ)
2026-01-13 17:24 Re: how to gate experimental features (SQL/PGQ) Tom Lane <[email protected]>
2026-01-15 17:05 ` Re: how to gate experimental features (SQL/PGQ) Andrew Dunstan <[email protected]>
@ 2026-01-15 17:23 ` Andres Freund <[email protected]>
1 sibling, 0 replies; 23+ messages in thread
From: Andres Freund @ 2026-01-15 17:23 UTC (permalink / raw)
To: Andrew Dunstan <[email protected]>; +Cc: Tom Lane <[email protected]>; Jacob Champion <[email protected]>; Peter Eisentraut <[email protected]>; David G. Johnston <[email protected]>; pgsql-hackers; Ashutosh Bapat <[email protected]>; Jelte Fennema-Nio <[email protected]>
Hi,
Sorry for the duplicate email, I somehow corrupted the last one.
On 2026-01-15 12:05:44 -0500, Andrew Dunstan wrote:
>
> On 2026-01-13 Tu 12:24 PM, Tom Lane wrote:
> > Jacob Champion<[email protected]> writes:
> > > On Tue, Jan 13, 2026 at 7:17 AM Andres Freund<[email protected]> wrote:
> > > > I don't even know how you could implement 3) realistically. We have zero
> > > > infrastructure for making e.g. parser, keyword list etc change due to defines
> > > > compile time.
> > > Is that an architecturally unsolvable thing, or is it a simple matter
> > > of programming? Would it be nice to have said infrastructure?
> > You'd have to throw out flex and bison and build some sort of
> > extensible parser. That has some attraction to me personally
> > (I worked on such systems decades ago at HP), but it's fairly
> > hard to justify the amount of effort that would be needed to
> > get there. It might well be slower than a flex/bison parser,
> > and/or have poorer detection of grammar inconsistencies, either
> > of which would be bad for our usage.
>
>
> Maybe, but maybe not. ISTR that gcc abandoned use of bison for their C
> compiler a long time ago, and that gnat's Ada compiler was hand cut from the
> get go.
>
> SQL is a different kettle of fish, of course - it dwarfs C and Ada in
> complexity.
The handwritten parser is also used for C++ which is *quite* a bit more
complicated than C, and probably roughly on-par with SQL.
I think the situation for C like languages is a bit different than with SQL
though, because typically the compiler specific syntax extensions are much
more modest than with SQL. Due to the different compilers for C like language,
it's probably easier to find grammar / language issues than for something like
postgres SQL dialect, which differs substantially from other SQL
implementations and thus only has a single parser.
That said, I do suspect we might eventually want to just give up on the
"parser generator as a sanity check" aspect and go with a hand written
recursive descent parser. For speed, extensibility and better error
recovery/messages.
Greetings,
Andres Freund
^ permalink raw reply [nested|flat] 23+ messages in thread
* Re: how to gate experimental features (SQL/PGQ)
2026-01-13 17:24 Re: how to gate experimental features (SQL/PGQ) Tom Lane <[email protected]>
2026-01-15 17:05 ` Re: how to gate experimental features (SQL/PGQ) Andrew Dunstan <[email protected]>
@ 2026-01-15 17:31 ` Tom Lane <[email protected]>
1 sibling, 0 replies; 23+ messages in thread
From: Tom Lane @ 2026-01-15 17:31 UTC (permalink / raw)
To: Andrew Dunstan <[email protected]>; +Cc: Jacob Champion <[email protected]>; Peter Eisentraut <[email protected]>; Andres Freund <[email protected]>; David G. Johnston <[email protected]>; pgsql-hackers; Ashutosh Bapat <[email protected]>; Jelte Fennema-Nio <[email protected]>
Andrew Dunstan <[email protected]> writes:
> On 2026-01-13 Tu 12:24 PM, Tom Lane wrote:
>> You'd have to throw out flex and bison and build some sort of
>> extensible parser. That has some attraction to me personally
>> (I worked on such systems decades ago at HP), but it's fairly
>> hard to justify the amount of effort that would be needed to
>> get there. It might well be slower than a flex/bison parser,
>> and/or have poorer detection of grammar inconsistencies, either
>> of which would be bad for our usage.
> Maybe, but maybe not. ISTR that gcc abandoned use of bison for their C
> compiler a long time ago, and that gnat's Ada compiler was hand cut from
> the get go.
> SQL is a different kettle of fish, of course - it dwarfs C and Ada in
> complexity.
Yeah. And we have additional problems besides the grammar being far
larger than it is for those projects:
* It's a moving target (to a much greater degree than C, anyway).
* A lot of our code is written by people who are not parser experts.
So it gives me great comfort that bison will complain if you hand it
an ambiguous or unsatisfiable grammar. If we went over to a
handwritten parser, I'd have next to no faith in it not being buggy.
There's good reasons why people put so much effort into parser
generators back in the day.
regards, tom lane
^ permalink raw reply [nested|flat] 23+ messages in thread
end of thread, other threads:[~2026-01-15 17:31 UTC | newest]
Thread overview: 23+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2020-08-17 20:20 [PATCH] Disable autovacuum for BRIN test table Alvaro Herrera <[email protected]>
2026-01-13 17:24 Re: how to gate experimental features (SQL/PGQ) Tom Lane <[email protected]>
2026-01-15 17:05 ` Re: how to gate experimental features (SQL/PGQ) Andrew Dunstan <[email protected]>
2026-01-15 17:23 ` Re: how to gate experimental features (SQL/PGQ) Andres Freund <[email protected]>
2026-01-15 17:31 ` Re: how to gate experimental features (SQL/PGQ) Tom Lane <[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