pg.ddx.io pgsql-general@postgresql.org mailing list archive
help / color / mirror / Atom feedConfusing error message in 15.6
2024-05-21 23:29 UTC Dmitry O Litvintsev <litvinse@fnal.gov>
` Re: Confusing error message in 15.6
2024-05-21 23:42 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Confusing error message in 15.6
2024-05-21 23:50 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Confusing error message in 15.6
2024-05-21 23:58 UTC Dmitry O Litvintsev <litvinse@fnal.gov>
` Re: Confusing error message in 15.6
2024-05-22 07:29 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[5+ messages in thread]
pg_stat_io clarifications: background worker, writes and reads
2024-05-14 20:26 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: pg_stat_io clarifications: background worker, writes and reads
2024-05-15 04:03 UTC Kashif Zeeshan <kashi.zeeshan@gmail.com>
` Re: pg_stat_io clarifications: background worker, writes and reads
2024-05-15 04:21 UTC Muhammad Imtiaz <imtiaz.m@bitnine.net>
` Re: pg_stat_io clarifications: background worker, writes and reads
2024-05-15 12:59 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: pg_stat_io clarifications: background worker, writes and reads
2024-05-15 14:32 UTC Kashif Zeeshan <kashi.zeeshan@gmail.com>
` Re: pg_stat_io clarifications: background worker, writes and reads
2024-05-21 19:20 UTC Dimitrios Apostolou <jimis@gmx.net>
[6+ messages in thread]
How to update upper-bound of tstzrange ?
2024-05-20 10:30 UTC Laura Smith <n5d9xq3ti233xiyif2vp@protonmail.ch>
` Re: How to update upper-bound of tstzrange ?
2024-05-20 10:48 UTC Kashif Zeeshan <kashi.zeeshan@gmail.com>
` Re: How to update upper-bound of tstzrange ?
2024-05-20 11:56 UTC Erik Wienhold <ewie@ewie.name>
` Re: How to update upper-bound of tstzrange ?
2024-05-21 10:02 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: How to update upper-bound of tstzrange ?
2024-05-21 10:37 UTC Laura Smith <n5d9xq3ti233xiyif2vp@protonmail.ch>
[5+ messages in thread]
pg_dump and not MVCC-safe commands
2024-05-19 02:24 UTC PetSerAl <petseral@gmail.com>
` Re: pg_dump and not MVCC-safe commands
2024-05-20 09:33 UTC Guillaume Lelarge <guillaume@lelarge.info>
` Re: pg_dump and not MVCC-safe commands
2024-05-20 10:36 UTC PetSerAl <petseral@gmail.com>
` Re: pg_dump and not MVCC-safe commands
2024-05-20 14:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump and not MVCC-safe commands
2024-05-20 15:49 UTC PetSerAl <petseral@gmail.com>
` Re: pg_dump and not MVCC-safe commands
2024-05-20 15:53 UTC Christophe Pettus <xof@thebuild.com>
` Re: pg_dump and not MVCC-safe commands
2024-05-20 20:10 UTC Ron Johnson <ronljohnsonjr@gmail.com>
[7+ messages in thread]
Updating 457 rows in a table
2024-05-19 16:54 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Updating 457 rows in a table
2024-05-19 16:56 UTC Christophe Pettus <xof@thebuild.com>
` Re: Updating 457 rows in a table
2024-05-19 16:57 UTC Ray O'Donnell <ray@rodonnell.ie>
` Re: Updating 457 rows in a table
2024-05-19 17:06 UTC Muhammad Ikram <mmikram@gmail.com>
` Re: Updating 457 rows in a table
2024-05-19 18:30 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Updating 457 rows in a table
2024-05-19 18:32 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Updating 457 rows in a table
2024-05-19 18:32 UTC Christophe Pettus <xof@thebuild.com>
` Re: Updating 457 rows in a table
2024-05-19 18:35 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Updating 457 rows in a table
2024-05-19 18:37 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Updating 457 rows in a table
2024-05-20 09:30 UTC Alban Hertroys <haramrae@gmail.com>
` Re: Updating 457 rows in a table
2024-05-20 12:33 UTC Rich Shepard <rshepard@appl-ecosys.com>
[11+ messages in thread]
signal 11: Segmentation fault ; query constraint list; pg16.3
2024-05-20 10:31 UTC milist ujang <ujang.milist@gmail.com>
` Re: signal 11: Segmentation fault ; query constraint list; pg16.3
2024-05-20 11:01 UTC David Rowley <dgrowleyml@gmail.com>
` Re: signal 11: Segmentation fault ; query constraint list; pg16.3
2024-05-20 11:18 UTC milist ujang <ujang.milist@gmail.com>
[3+ messages in thread]
Left join syntax error
2024-05-18 12:52 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Left join syntax error
2024-05-18 13:19 UTC Shammat <shammat@gmx.net>
` Re: Left join syntax error
2024-05-18 14:46 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Left join syntax error
2024-05-18 14:49 UTC Ray O'Donnell <ray@rodonnell.ie>
` Re: Left join syntax error
2024-05-18 14:49 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Left join syntax error
2024-05-18 15:00 UTC Erik Wienhold <ewie@ewie.name>
` Re: Left join syntax error
2024-05-18 15:01 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Left join syntax error
2024-05-18 15:03 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Left join syntax error
2024-05-18 15:04 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Left join syntax error
2024-05-18 15:04 UTC Ray O'Donnell <ray@rodonnell.ie>
` Re: Left join syntax error
2024-05-18 15:12 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Left join syntax error
2024-05-18 15:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Left join syntax error
2024-05-18 15:14 UTC Erik Wienhold <ewie@ewie.name>
` Re: Left join syntax error
2024-05-18 15:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Left join syntax error
2024-05-18 15:18 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Left join syntax error
2024-05-18 15:27 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Left join syntax error
2024-05-18 15:30 UTC Erik Wienhold <ewie@ewie.name>
` Re: Left join syntax error
2024-05-18 15:38 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Left join syntax error
2024-05-18 15:40 UTC Rich Shepard <rshepard@appl-ecosys.com>
` Re: Left join syntax error
2024-05-18 15:41 UTC Rich Shepard <rshepard@appl-ecosys.com>
[20+ messages in thread]
utf8 vs UTF-8
2024-05-17 12:44 UTC Troels Arvin <troels@arvin.dk>
` Re: utf8 vs UTF-8
2024-05-17 13:49 UTC Hans Schou <hans.schou@gmail.com>
` Re: utf8 vs UTF-8
2024-05-17 13:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: utf8 vs UTF-8
2024-05-18 14:19 UTC Troels Arvin <troels@arvin.dk>
` Re: utf8 vs UTF-8
2024-05-18 14:48 UTC Troels Arvin <troels@arvin.dk>
` Re: utf8 vs UTF-8
2024-05-18 15:01 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: utf8 vs UTF-8
2024-05-18 15:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
Valid until
2024-05-14 07:57 UTC Rama Krishnan <raghuldrag@gmail.com>
` Re: Valid until
2024-05-14 15:27 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Valid until
2024-05-14 15:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Valid until
2024-05-14 15:52 UTC Muhammad Imtiaz <imtiaz.m@bitnine.net>
` Re: Valid until
2024-05-18 14:40 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Valid until
2024-05-18 14:48 UTC Adrian Klaver <adrian.klaver@aklaver.com>
[6+ messages in thread]
Execution history of a single query
2024-05-17 16:42 UTC arun chirappurath <arunsnmimt@gmail.com>
` Re: Execution history of a single query
2024-05-17 17:23 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: Execution history of a single query
2024-05-17 23:05 UTC Julien Rouhaud <rjuju123@gmail.com>
[3+ messages in thread]
pg_upgrade can result in early wraparound on databases with high transaction load
2019-05-20 10:10 UTC Jason Harvey <jason@reddit.com>
` Re: pg_upgrade can result in early wraparound on databases with high transaction load
2019-05-21 22:23 UTC Peter Geoghegan <pg@bowt.ie>
` Re: pg_upgrade can result in early wraparound on databases with high transaction load
2019-06-15 18:37 UTC Noah Misch <noah@leadboat.com>
` Re: pg_upgrade can result in early wraparound on databases with high transaction load
2021-04-23 23:42 UTC Andres Freund <andres@anarazel.de>
` Re: pg_upgrade can result in early wraparound on databases with high transaction load
2021-04-24 00:28 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: pg_upgrade can result in early wraparound on databases with high transaction load
2021-04-24 01:00 UTC Andres Freund <andres@anarazel.de>
` Re: pg_upgrade can result in early wraparound on databases with high transaction load
2021-05-04 08:17 UTC Drouvot, Bertrand <bdrouvot@amazon.com>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2021-07-27 02:39 UTC Bruce Momjian <bruce@momjian.us>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2021-07-27 07:25 UTC Drouvot, Bertrand <bdrouvot@amazon.com>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2021-07-27 12:50 UTC Bruce Momjian <bruce@momjian.us>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2022-07-05 16:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2022-07-05 18:52 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2022-07-05 19:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2022-07-05 19:41 UTC Peter Geoghegan <pg@bowt.ie>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2022-07-05 19:50 UTC Peter Geoghegan <pg@bowt.ie>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2022-07-05 21:25 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: [UNVERIFIED SENDER] Re: pg_upgrade can result in early wraparound on databases with high transaction load
2022-07-05 22:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [UNVERIFIED SENDER] pg_upgrade can result in early wraparound on databases with high transaction load
2024-05-16 06:11 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: [UNVERIFIED SENDER] pg_upgrade can result in early wraparound on databases with high transaction load
2024-05-16 17:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [UNVERIFIED SENDER] pg_upgrade can result in early wraparound on databases with high transaction load
2024-05-17 12:35 UTC Daniel Gustafsson <daniel@yesql.se>
[20+ messages in thread]
Do we have any email discussions related to SQL rate limiting?
2024-05-17 06:59 UTC Benjamin Mitchell <benjaminmitchell@foxmail.com>
` Re: Do we have any email discussions related to SQL rate limiting?
2024-05-17 11:56 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
db was corrupted, ERROR: cannot freeze committed xmax; fix by deleting rows in catalog tables
2024-05-16 04:01 UTC milist ujang <ujang.milist@gmail.com>
Seeing new stuff in log after upgrading from 11 to 15
2024-05-15 23:27 UTC Dmitry O Litvintsev <litvinse@fnal.gov>
` Re: Seeing new stuff in log after upgrading from 11 to 15
2024-05-15 23:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Seeing new stuff in log after upgrading from 11 to 15
2024-05-16 00:00 UTC Dmitry O Litvintsev <litvinse@fnal.gov>
[3+ messages in thread]
Sequence values change during upgrade
2024-05-15 08:03 UTC Danut Soare <danut_soare@yahoo.com>
` Re: Sequence values change during upgrade
2024-05-15 11:01 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Sequence values change during upgrade
2024-05-15 12:17 UTC Danut Soare <danut_soare@yahoo.com>
` Re: Sequence values change during upgrade
2024-05-15 14:29 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
Adding constraints faster
2024-05-14 19:59 UTC sud <suds1434@gmail.com>
` Re: Adding constraints faster
2024-05-15 03:02 UTC sud <suds1434@gmail.com>
[2+ messages in thread]
Using ALTER TABLE DETACH PARTITION CONCURRENTLY inside a procedure
2024-05-14 20:24 UTC Dirschel, Steve <steve.dirschel@thomsonreuters.com>
` Re: Using ALTER TABLE DETACH PARTITION CONCURRENTLY inside a procedure
2024-05-14 20:45 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-10 18:38 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-10 19:24 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-10 19:35 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-10 20:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-11 01:10 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-11 01:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-11 01:35 UTC David Rowley <dgrowleyml@gmail.com>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-11 01:37 UTC David Rowley <dgrowleyml@gmail.com>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 12:27 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 12:41 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 12:46 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 13:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 13:32 UTC David Rowley <dgrowleyml@gmail.com>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 13:34 UTC David Rowley <dgrowleyml@gmail.com>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 13:52 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 14:07 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 14:15 UTC David Rowley <dgrowleyml@gmail.com>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-13 14:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-14 12:55 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-14 16:14 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-14 18:11 UTC Dimitrios Apostolou <jimis@gmx.net>
` Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions
2024-05-14 18:26 UTC Dimitrios Apostolou <jimis@gmx.net>
[22+ messages in thread]
UTC is not a time zone?
2024-05-13 17:37 UTC Christophe Pettus <xof@thebuild.com>
` Re: UTC is not a time zone?
2024-05-13 17:48 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: UTC is not a time zone?
2024-05-13 17:50 UTC Christophe Pettus <xof@thebuild.com>
` Re: UTC is not a time zone?
2024-05-13 17:53 UTC Erik Wienhold <ewie@ewie.name>
` Re: UTC is not a time zone?
2024-05-13 17:58 UTC Christophe Pettus <xof@thebuild.com>
` Re: UTC is not a time zone?
2024-05-13 17:58 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: UTC is not a time zone?
2024-05-13 18:02 UTC Christophe Pettus <xof@thebuild.com>
` Re: UTC is not a time zone?
2024-05-13 18:07 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: UTC is not a time zone?
2024-05-13 18:09 UTC Christophe Pettus <xof@thebuild.com>
` Re: UTC is not a time zone?
2024-05-13 18:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: UTC is not a time zone?
2024-05-13 18:18 UTC Christophe Pettus <xof@thebuild.com>
` Re: UTC is not a time zone?
2024-05-13 18:26 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: UTC is not a time zone?
2024-05-13 18:27 UTC Christophe Pettus <xof@thebuild.com>
` Re: UTC is not a time zone?
2024-05-13 18:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: UTC is not a time zone?
2024-05-13 18:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
[15+ messages in thread]
how to completely turn off statement error logging
2024-05-13 14:10 UTC Zwettler Markus (OIZ) <Markus.Zwettler@zuerich.ch>
` Re: how to completely turn off statement error logging
2024-05-13 14:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: how to completely turn off statement error logging
2024-05-13 15:14 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
AW: [Extern] Re: how to completely turn off statement error logging
2024-05-13 15:00 UTC Zwettler Markus (OIZ) <Markus.Zwettler@zuerich.ch>
Postgresql active-active nodes in cluster
2024-05-09 06:54 UTC Vidyashree H S <Shreevidya.hs@exaleapsemi.com>
` Re: Postgresql active-active nodes in cluster
2024-05-09 10:58 UTC Kashif Zeeshan <kashi.zeeshan@gmail.com>
` Re: Postgresql active-active nodes in cluster
2024-05-09 22:33 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: Postgresql active-active nodes in cluster
2024-05-09 23:23 UTC Bruce Momjian <bruce@momjian.us>
` Re: Postgresql active-active nodes in cluster
2024-05-10 05:18 UTC Vidyashree H S <Shreevidya.hs@exaleapsemi.com>
` Re: Postgresql active-active nodes in cluster
2024-05-13 06:38 UTC Vidyashree H S <Shreevidya.hs@exaleapsemi.com>
` Re: Postgresql active-active nodes in cluster
2024-05-13 14:13 UTC Greg Sabino Mullane <htamfids@gmail.com>
[7+ messages in thread]
Feature Request: Option for TLS no SSLRequest with psql
2024-05-11 15:19 UTC AJ ONeal <coolaj86@proton.me>
` Re: Feature Request: Option for TLS no SSLRequest with psql
2024-05-11 15:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Feature Request: Option for TLS no SSLRequest with psql
2024-05-11 15:59 UTC Joe Conway <mail@joeconway.com>
` Re: Feature Request: Option for TLS no SSLRequest with psql
2024-05-11 16:01 UTC Joe Conway <mail@joeconway.com>
[4+ messages in thread]
Feature Request: Add "pg" as TLS-ALPN
2024-05-11 15:34 UTC AJ ONeal <coolaj86@proton.me>
Unnecessary buffer usage with multicolumn index, row comparison, and equility constraint
2024-05-11 03:27 UTC WU Yan <4wuyan@gmail.com>
` Re: Unnecessary buffer usage with multicolumn index, row comparison, and equility constraint
2024-05-11 04:05 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: Unnecessary buffer usage with multicolumn index, row comparison, and equility constraint
2024-05-11 04:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
[next (older)]
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox