pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Bug in copy
  2025-02-08 05:28 UTC  me nefcanto <sn.1361@gmail.com>
` Re: Bug in copy
  2025-02-08 05:45 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug in copy
  2025-02-08 05:52 UTC  Zhang Mingli <zmlpostgres@gmail.com>
` Re: Bug in copy
  2025-02-08 06:01 UTC  me nefcanto <sn.1361@gmail.com>
` Re: Bug in copy
  2025-02-08 06:11 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug in copy
  2025-02-09 06:02 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Bug in copy
  2025-02-09 12:30 UTC  me nefcanto <sn.1361@gmail.com>
` Re: Bug in copy
  2025-02-09 12:33 UTC  me nefcanto <sn.1361@gmail.com>
` Re: Bug in copy
  2025-02-09 14:13 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug in copy
  2025-02-09 16:39 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Bug in copy
  2025-02-24 14:09 UTC  me nefcanto <sn.1361@gmail.com>
` Re: Bug in copy
  2025-02-24 15:55 UTC  Greg Sabino Mullane <htamfids@gmail.com>
` Re: Bug in copy
  2025-02-25 06:46 UTC  me nefcanto <sn.1361@gmail.com>
` Re: Bug in copy
  2025-02-25 13:15 UTC  Greg Sabino Mullane <htamfids@gmail.com>
  [14+ messages in thread]

Bug in Configuration Setting Functions after a Commit
  2025-02-24 18:26 UTC  João felipe Chiarelli Bourscheid <joao.felipe.c.b@gmail.com>
` Re: Bug in Configuration Setting Functions after a Commit
  2025-02-24 18:38 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug in Configuration Setting Functions after a Commit
  2025-02-24 18:49 UTC  João felipe Chiarelli Bourscheid <joao.felipe.c.b@gmail.com>
` Re: Bug in Configuration Setting Functions after a Commit
  2025-02-24 18:56 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [4+ messages in thread]

Possible Bug in JSON_QUERY() Behavior in PostgreSQL 17
  2025-02-20 11:01 UTC  Susmitha S <susmithaselvarani.ds@gmail.com>
` Re: Possible Bug in JSON_QUERY() Behavior in PostgreSQL 17
  2025-02-20 11:31 UTC  Susmitha S <susmithaselvarani.ds@gmail.com>
` Re: Possible Bug in JSON_QUERY() Behavior in PostgreSQL 17
  2025-02-20 12:35 UTC  Junwang Zhao <zhjwpku@gmail.com>
` Re: Possible Bug in JSON_QUERY() Behavior in PostgreSQL 17
  2025-02-23 03:18 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [4+ messages in thread]

BUG #18823: pg_restore not work
  2025-02-22 15:28 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18823: pg_restore not work
  2025-02-22 16:34 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

Re: DKIM signature rejected
  2025-02-22 12:06 UTC  Matthias Apitz <guru@unixarea.de>

BUG #18821: Need delete files in pg_wal, size is bigger overcome limit max_wal_size
  2025-02-20 17:42 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18821: Need delete files in pg_wal, size is bigger overcome limit max_wal_size
  2025-02-20 19:33 UTC  Marlene Saransig <marle.saransig@gmail.com>
` Re: BUG #18821: Need delete files in pg_wal, size is bigger overcome limit max_wal_size
  2025-02-21 10:51 UTC  hubert depesz lubaczewski <depesz@depesz.com>
  [3+ messages in thread]

Error in form on site commitfest.postgresql.org
  2025-02-13 12:46 UTC  Vladlen Popolitov <v.popolitov@postgrespro.ru>
` Re: Error in form on site commitfest.postgresql.org
  2025-02-13 14:41 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: Error in form on site commitfest.postgresql.org
  2025-02-21 04:57 UTC  Vladlen Popolitov <v.popolitov@postgrespro.ru>
` Re: Error in form on site commitfest.postgresql.org
  2025-02-21 09:23 UTC  Jelte Fennema-Nio <me@jeltef.nl>
  [4+ messages in thread]

BUG #18820: Issue with Installation Due to Space in User Profile Path
  2025-02-20 06:24 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18820: Issue with Installation Due to Space in User Profile Path
  2025-02-20 10:12 UTC  Manika Singhal <manika.singhal@enterprisedb.com>
  [2+ messages in thread]

Possible bug ¿? missing "ucol.h" in postgre installation
  2025-02-17 19:18 UTC  Jose Fco. Mojada <jfmojada@yahoo.es>
` Re: Possible bug ¿? missing "ucol.h" in postgre installation
  2025-02-17 19:47 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Possible bug ¿? missing "ucol.h" in postgre installation
  2025-02-17 20:16 UTC  Jose Fco. Mojada <jfmojada@yahoo.es>
` Re: Possible bug ¿? missing "ucol.h" in postgre installation
  2025-02-19 19:14 UTC  Jose Fco. Mojada <jfmojada@yahoo.es>
  [4+ messages in thread]

BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2024-08-28 16:17 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2024-08-28 17:56 UTC  Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2024-08-29 00:02 UTC  Francisco J. Ossandón <fco.j.ossandon@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2024-08-29 00:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2024-08-29 00:33 UTC  Francisco J. Ossandón <fco.j.ossandon@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-01-22 10:00 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-02-17 22:31 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-02-17 22:49 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-02-17 23:12 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-02-17 23:39 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-02-18 02:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-02-19 12:50 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-02-19 13:46 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE
  2025-02-19 19:02 UTC  Vik Fearing <vik@postgresfriends.org>
  [14+ messages in thread]

BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-18 08:21 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-18 12:21 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-18 12:52 UTC  Indrajeeth Deshmukh <bkindrajeeth@gmail.com>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-18 14:37 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-18 14:38 UTC  Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-18 15:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-19 05:57 UTC  Matthias Apitz <guru@unixarea.de>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-19 06:30 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-19 06:39 UTC  Daniel Westermann (DWE) <daniel.westermann@dbi-services.com>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-19 08:58 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-19 10:00 UTC  Matthias Apitz <guru@unixarea.de>
` Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs
  2025-02-19 17:48 UTC  Greg Sabino Mullane <htamfids@gmail.com>
  [12+ messages in thread]

Inconsistency of timezones in postgresql
  2024-07-31 10:55 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 11:50 UTC  Aleksander Alekseev <aleksander@timescale.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 12:31 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 12:35 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 12:52 UTC  Aleksander Alekseev <aleksander@timescale.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 13:06 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 13:23 UTC  Aleksander Alekseev <aleksander@timescale.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 14:07 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 14:35 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 14:51 UTC  Aleksander Alekseev <aleksander@timescale.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 15:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 15:16 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 15:34 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 17:14 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 17:42 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-07-31 19:03 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-01 01:37 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-01 01:51 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-01 01:58 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-01 03:35 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-01 04:28 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-01 05:06 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-01 10:24 UTC  Aleksander Alekseev <aleksander@timescale.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-02 04:13 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-02 04:18 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-02 04:22 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-02 04:55 UTC  Chris BSomething <xpusostomos@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-02 05:08 UTC  Christophe Pettus <xof@thebuild.com>
` Re: Inconsistency of timezones in postgresql
  2024-08-02 05:45 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistency of timezones in postgresql
  2025-01-29 13:09 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Inconsistency of timezones in postgresql
  2025-02-18 20:52 UTC  Bruce Momjian <bruce@momjian.us>
` Re: Inconsistency of timezones in postgresql
  2025-02-19 08:53 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [32+ messages in thread]

BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 07:01 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 07:38 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re:Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 08:55 UTC  =?GBK?B?w8/B7rHy?= <m_lingbin@126.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 09:48 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 11:48 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 12:11 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 12:20 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 12:33 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 13:55 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 14:04 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-12 14:30 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-13 02:39 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-13 03:14 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-13 04:55 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-13 07:25 UTC  Tender Wang <tndrwang@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-18 02:53 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-18 04:22 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-18 05:03 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-18 06:52 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-19 02:28 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-19 02:42 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally
  2025-02-19 04:59 UTC  Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
  [22+ messages in thread]

BUG #18818: Access to postgres repo
  2025-02-18 16:38 UTC  PG Bug reporting form <noreply@postgresql.org>

PG17 --transaction-size=1000 caused MVU failure
  2025-02-18 09:08 UTC  Virender Singla <virender.cse@gmail.com>

Limitation in `pg_lsclusters` and `pg_dropcluster --stop` on Debian-based Systems
  2025-02-18 05:04 UTC  AKASH <akashbhujbal7051@gmail.com>
` Re: Limitation in `pg_lsclusters` and `pg_dropcluster --stop` on Debian-based Systems
  2025-02-18 05:17 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Limitation in `pg_lsclusters` and `pg_dropcluster --stop` on Debian-based Systems
  2025-02-18 05:24 UTC  AKASH <akashbhujbal7051@gmail.com>
  [3+ messages in thread]

BUG #18814: cannot read properties of undefined (reading 'notifies')
  2025-02-17 07:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18814: cannot read properties of undefined (reading 'notifies')
  2025-02-17 15:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18816: pg16 requires perl 5.14+ but is not documented
  2025-02-17 15:09 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18816: pg16 requires perl 5.14+ but is not documented
  2025-02-17 15:44 UTC  Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #18816: pg16 requires perl 5.14+ but is not documented
  2025-02-17 15:45 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

(Bug? or Intended?) Inconsistent search_path Behavior in Function Calls via Materialized View in PostgreSQL 17
  2025-02-17 15:10 UTC  Kanitchet Vaiassava <kanichet@hotmail.com>
` Re: (Bug? or Intended?) Inconsistent search_path Behavior in Function Calls via Materialized View in PostgreSQL 17
  2025-02-17 15:34 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

issue with PSQL 17.1 on Suse 15 Linux SP6
  2025-02-17 12:19 UTC  Raghu Dev Ramaiah <rramaiah@opentext.com>
` Re: issue with PSQL 17.1 on Suse 15 Linux SP6
  2025-02-17 15:31 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18812: Conditional rule: inconsistent check for statement
  2025-02-14 21:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18812: Conditional rule: inconsistent check for statement
  2025-02-14 22:55 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18812: Conditional rule: inconsistent check for statement
  2025-02-17 10:58 UTC  Boris P. Korzun <drtr0jan@yandex.ru>
  [3+ messages in thread]

BUG #18813: Materialized view creation regression when inlining recursive SQL function
  2025-02-16 15:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18813: Materialized view creation regression when inlining recursive SQL function
  2025-02-16 16:24 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18813: Materialized view creation regression when inlining recursive SQL function
  2025-02-16 17:33 UTC  Olivier Jolly <zeograd@gmail.com>
  [3+ messages in thread]

BUG #18810: invalid value for parameter "synchronized_standby_slots" Caused error:"Segmentation fault"
  2025-02-13 10:43 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18810: invalid value for parameter "synchronized_standby_slots" Caused error:"Segmentation fault"
  2025-02-13 14:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18811: PANIC,XX000,"WAL contains references to invalid pages"
  2025-02-13 12:19 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #18809: Inconsistent JSON behavoir
  2025-02-13 03:22 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18809: Inconsistent JSON behavoir
  2025-02-13 05:24 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18809: Inconsistent JSON behavoir
  2025-02-13 06:06 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