pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18089: Orphaned Rows During PostgreSQL Data Migration
2023-09-05 13:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18089: Orphaned Rows During PostgreSQL Data Migration
2023-09-06 04:13 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
pg_dump assertion failure with "-n pg_catalog"
2023-06-07 17:36 UTC Jeff Davis <pgsql@j-davis.com>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-06-12 06:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-06-15 22:47 UTC Jeff Davis <pgsql@j-davis.com>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-06-16 05:29 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-06-16 17:29 UTC Jeff Davis <pgsql@j-davis.com>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-08-22 20:10 UTC Jeff Davis <pgsql@j-davis.com>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-09-05 09:45 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-09-05 22:33 UTC Jeff Davis <pgsql@j-davis.com>
[8+ messages in thread]
BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio
2023-09-05 13:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio
2023-09-05 17:44 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18086: compilation failed due to epoll_create1 not present
2023-09-05 10:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18086: compilation failed due to epoll_create1 not present
2023-09-05 11:51 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18086: compilation failed due to epoll_create1 not present
2023-09-05 13:26 UTC Duke Astar <dukeastar@gmail.com>
[3+ messages in thread]
BUG #18085: Error in documentation
2023-09-05 09:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18085: Error in documentation
2023-09-05 13:14 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
BUG #18087: pg_visibility: false positives in pg_check_visible
2023-09-05 13:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18087: pg_visibility: false positives in pg_check_visible
2023-09-05 13:12 UTC huyajun <hu_yajun@qq.com>
[2+ messages in thread]
BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-04 17:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 01:51 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 02:25 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 08:57 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 09:52 UTC Navadvipa Chandra das <navadvipa.chandra.das@nizhnyaya-navadvipa.ru>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 12:55 UTC Daniel Gustafsson <daniel@yesql.se>
[6+ messages in thread]
BUG #18081: Spurious "function with OID ###### does not exist" error
2023-09-04 09:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18081: Spurious "function with OID ###### does not exist" error
2023-09-04 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18081: Spurious "function with OID ###### does not exist" error
2023-09-05 11:57 UTC Branko Radovanovic <branko.radovanovic.zg@gmail.com>
[3+ messages in thread]
BUG #18082: coredump during initdb
2023-09-04 14:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18082: coredump during initdb
2023-09-04 15:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18082: coredump during initdb
2023-09-05 07:33 UTC Duke Astar <dukeastar@gmail.com>
` Re: BUG #18082: coredump during initdb
2023-09-05 10:21 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #18082: coredump during initdb
2023-09-05 11:01 UTC Duke Astar <dukeastar@gmail.com>
[5+ messages in thread]
BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-05-29 20:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-06-17 14:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-08-13 13:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-08-13 14:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-08-13 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-09-04 06:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-09-04 14:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-09-05 04:58 UTC Michael Paquier <michael@paquier.xyz>
[8+ messages in thread]
UPDATE mentions the RETURNING * syntax but does not mention RETURNING * INTO ...
2023-09-04 15:55 UTC James Stuart <slim2k@privatejuris.org>
` Re: UPDATE mentions the RETURNING * syntax but does not mention RETURNING * INTO ...
2023-09-04 21:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 10:34 UTC Romain MAZIÈRE <romain.maziere@sigmaz-consilium.fr>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 10:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 11:00 UTC Romain MAZIÈRE <romain.maziere@sigmaz-consilium.fr>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 12:02 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 12:13 UTC Romain MAZIÈRE <romain.maziere@sigmaz-consilium.fr>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 12:25 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[6+ messages in thread]
BUG #18078: createdb not working
2023-08-31 15:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18078: createdb not working
2023-08-31 16:20 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18078: createdb not working
2023-08-31 16:54 UTC Orhan Punar <exaltedsoft@gmail.com>
` Re: BUG #18078: createdb not working
2023-08-31 17:12 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #18078: createdb not working
2023-08-31 17:21 UTC Orhan Punar <exaltedsoft@gmail.com>
` Re: BUG #18078: createdb not working
2023-08-31 17:37 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18078: createdb not working
2023-08-31 17:41 UTC Orhan Punar <exaltedsoft@gmail.com>
` Re: BUG #18078: createdb not working
2023-08-31 19:59 UTC Andrew Dunstan <andrew@dunslane.net>
[8+ messages in thread]
BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-29 20:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-29 21:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-29 21:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 07:58 UTC Emile Amewoto <emileam@yahoo.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 16:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:12 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:24 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:24 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:25 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:26 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:27 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 22:12 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 22:14 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
[13+ messages in thread]
BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
2023-08-29 20:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
2023-08-29 21:37 UTC Robert Sanford <wobbet@gmail.com>
` Re: BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
2023-08-30 13:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
2023-08-30 20:44 UTC Robert Sanford <wobbet@gmail.com>
[4+ messages in thread]
Where Clause not being applied to all tables in a publication
2023-08-30 18:43 UTC Brad Nicholson <brad.nicholson@instacart.com>
` Re: Where Clause not being applied to all tables in a publication
2023-08-30 18:46 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18074: After enabling JIT, the query runtime increased by over a thousand times.
2023-08-29 06:42 UTC PG Bug reporting form <noreply@postgresql.org>
problem with segmentation fault error
2010-01-27 21:27 UTC pg2@onet.eu
` Re: problem with segmentation fault error
2010-01-27 23:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` cache lookup failed dropping public schema with trgm index
2023-08-21 18:40 UTC Wyatt Alt <wyatt.alt@gmail.com>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 22:09 UTC Michael Paquier <michael@paquier.xyz>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 22:36 UTC Andres Freund <andres@anarazel.de>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 22:55 UTC Michael Paquier <michael@paquier.xyz>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 23:13 UTC Wyatt Alt <wyatt.alt@gmail.com>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 23:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-22 01:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-22 18:45 UTC Andres Freund <andres@anarazel.de>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-28 02:15 UTC Michael Paquier <michael@paquier.xyz>
[11+ messages in thread]
BUG #5261: Invalide page header
2010-01-04 13:44 UTC Takesver Kumar Thakur <takesver.thakur@mobilefundas.com>
` Re: BUG #5261: Invalide page header
2010-01-04 19:28 UTC Robert Haas <robertmhaas@gmail.com>
` BUG #18069: pg_is_in_recovery() is false but recovery is not yet completed(i.e. recovery.signal is present)
2023-08-25 06:40 UTC PG Bug reporting form <noreply@postgresql.org>
[3+ messages in thread]
BUG #18068: Insufficient permission unless SUPERUSER
2023-08-24 02:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18068: Insufficient permission unless SUPERUSER
2023-08-24 12:49 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18068: Insufficient permission unless SUPERUSER
2023-08-25 00:17 UTC Ghw <ghw@ghwfluffy.com>
[3+ messages in thread]
Error when using unquoted identifier that contains the word end in a begin atomic block
2023-08-24 19:53 UTC Jonathan Zacharuk <jonathan.zacharuk@ascentech.ca>
` Re: Error when using unquoted identifier that contains the word end in a begin atomic block
2023-08-24 20:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: Error when using unquoted identifier that contains the word end in a begin atomic block
2023-08-24 20:23 UTC Jonathan Zacharuk <jonathan.zacharuk@ascentech.ca>
[3+ messages in thread]
BUG #18059: Unexpected error 25001 in stored procedure
2023-08-17 14:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18059: Unexpected error 25001 in stored procedure
2023-08-19 17:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18059: Unexpected error 25001 in stored procedure
2023-08-21 13:32 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18059: Unexpected error 25001 in stored procedure
2023-08-22 21:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18059: Unexpected error 25001 in stored procedure
2023-08-23 20:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #18067: Droping function that was used to generate column drops the column, even after `DROP EXPRESSION`
2023-08-22 18:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18067: Droping function that was used to generate column drops the column, even after `DROP EXPRESSION`
2023-08-23 19:26 UTC Euler Taveira <euler@eulerto.com>
[2+ messages in thread]
BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-22 09:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-22 12:51 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-22 13:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-22 13:45 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-23 11:40 UTC kaijian xu <a17764530215@gmail.com>
[5+ messages in thread]
BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-24 13:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 18:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 19:44 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 19:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 20:54 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 21:57 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 13:56 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 14:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 18:57 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 19:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 20:30 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 22:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 12:11 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 12:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 13:23 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 13:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 18:43 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 19:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-01 13:14 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-02 21:54 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-02 21:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-02 22:13 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-03 02:15 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-08 12:48 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-10 19:51 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-11 14:15 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-12 20:08 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-15 07:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-17 14:27 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-21 12:33 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-21 16:04 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-21 16:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-22 19:22 UTC Andrew Dunstan <andrew@dunslane.net>
[33+ 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