pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18321: My first name and my name are reverse
2024-02-01 11:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18321: My first name and my name are reverse
2024-02-01 12:40 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18321: My first name and my name are reverse
2024-02-01 12:42 UTC Daniel Gustafsson <daniel@yesql.se>
[3+ messages in thread]
BUG #18320: Duplicate primary key records in table
2024-02-01 01:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18320: Duplicate primary key records in table
2024-02-01 02:32 UTC vishnu rao <jaihind213@gmail.com>
` BUG #18320: Duplicate primary key records in table
2024-02-01 08:03 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
Cascade rules on INSERT wrong behaviour on 16.0
2024-01-31 13:44 UTC Oleksandr Voytsekhovskyy <young.inbox@gmail.com>
` Re: Cascade rules on INSERT wrong behaviour on 16.0
2024-01-31 15:52 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #18318: Different character codes are mixed in the log file in Japanese locale.
2024-01-31 09:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18318: Different character codes are mixed in the log file in Japanese locale.
2024-01-31 15:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18316: The descriptions of the objoid and classoid fields in the pg_description section, include: 12,14,16
2024-01-31 02:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18316: The descriptions of the objoid and classoid fields in the pg_description section, include: 12,14,16
2024-01-31 10:19 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-25 04:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-26 02:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-26 03:23 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-26 03:33 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-26 03:41 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-26 04:54 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-26 06:21 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-27 17:32 UTC Yongtao Huang <yongtaoh2022@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-28 23:18 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-28 23:34 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-29 03:27 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-30 01:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-30 06:28 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-30 07:29 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-30 07:42 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-30 08:02 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-30 08:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-30 11:51 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-31 04:25 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self
2024-01-31 08:11 UTC Tender Wang <tndrwang@gmail.com>
[20+ messages in thread]
BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-15 11:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-24 10:11 UTC gparc@free.fr
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-24 14:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-24 15:28 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-24 16:01 UTC gparc@free.fr
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-25 15:36 UTC gparc@free.fr
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-26 10:54 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-26 11:33 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-26 12:14 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-26 13:19 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-26 13:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-29 08:42 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-29 08:59 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-29 21:18 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
2024-01-30 07:28 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[15+ messages in thread]
Misleading/inaccurate error message from pg_basebackup
2024-01-22 16:47 UTC c@osss.net
` Re: Misleading/inaccurate error message from pg_basebackup
2024-01-23 10:27 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Misleading/inaccurate error message from pg_basebackup
2024-01-23 17:37 UTC Casey <c@osss.net>
` Re: Misleading/inaccurate error message from pg_basebackup
2024-01-23 23:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: Misleading/inaccurate error message from pg_basebackup
2024-01-24 09:20 UTC Christoph Berg <myon@debian.org>
` Re: Misleading/inaccurate error message from pg_basebackup
2024-01-24 12:48 UTC Christoph Berg <myon@debian.org>
` Re: Misleading/inaccurate error message from pg_basebackup
2024-01-29 17:40 UTC Christoph Berg <myon@debian.org>
` Re: Misleading/inaccurate error message from pg_basebackup
2024-01-29 21:14 UTC Casey <c@osss.net>
[8+ messages in thread]
BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-10 12:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-10 13:56 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-12 02:00 UTC Andy Fan <zhihuifan1213@163.com>
` Re: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-23 11:42 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-23 12:27 UTC feichanghong <feichanghong@qq.com>
` RE: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-23 12:33 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-24 09:18 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-24 10:00 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-24 11:01 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-25 03:58 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18280: logical decoding build wrong snapshot for subtransactions
2024-01-29 09:24 UTC Amit Kapila <amit.kapila16@gmail.com>
[11+ messages in thread]
BUG #18313: No error triggered when subtracting an interval from a timestamp
2024-01-26 13:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18313: No error triggered when subtracting an interval from a timestamp
2024-01-26 17:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18016: REINDEX TABLE failure
2023-07-06 20:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18016: REINDEX TABLE failure
2023-07-08 00:17 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18016: REINDEX TABLE failure
2023-07-08 00:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18016: REINDEX TABLE failure
2023-07-09 07:01 UTC Gurjeet Singh <gurjeet@singh.im>
` Re: BUG #18016: REINDEX TABLE failure
2023-07-09 07:55 UTC Michael Paquier <michael@paquier.xyz>
` RE: BUG #18016: REINDEX TABLE failure
2023-07-09 13:54 UTC Richard Veselý <richard.vesely@softea.sk>
` Re: BUG #18016: REINDEX TABLE failure
2023-07-09 14:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18016: REINDEX TABLE failure
2023-07-10 16:35 UTC Gurjeet Singh <gurjeet@singh.im>
` Re: BUG #18016: REINDEX TABLE failure
2023-07-10 16:43 UTC Gurjeet Singh <gurjeet@singh.im>
` RE: BUG #18016: REINDEX TABLE failure
2023-07-11 09:31 UTC Richard Veselý <richard.vesely@softea.sk>
` Re: BUG #18016: REINDEX TABLE failure
2023-07-26 20:16 UTC Nathan Bossart <nathandbossart@gmail.com>
` Fwd: BUG #18016: REINDEX TABLE failure
2023-07-27 01:42 UTC Gurjeet Singh <gurjeet@singh.im>
` Fwd: BUG #18016: REINDEX TABLE failure
2023-07-27 01:43 UTC Gurjeet Singh <gurjeet@singh.im>
` Re: Fwd: BUG #18016: REINDEX TABLE failure
2023-07-27 23:10 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Fwd: BUG #18016: REINDEX TABLE failure
2023-07-27 23:14 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Fwd: BUG #18016: REINDEX TABLE failure
2023-07-28 01:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: Fwd: BUG #18016: REINDEX TABLE failure
2023-07-28 18:00 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Fwd: BUG #18016: REINDEX TABLE failure
2023-09-01 16:55 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Fwd: BUG #18016: REINDEX TABLE failure
2023-11-29 21:43 UTC Gurjeet Singh <gurjeet@singh.im>
` Re: Fwd: BUG #18016: REINDEX TABLE failure
2024-01-26 02:52 UTC vignesh C <vignesh21@gmail.com>
` Re: Fwd: BUG #18016: REINDEX TABLE failure
2024-01-26 09:22 UTC Michael Paquier <michael@paquier.xyz>
[21+ messages in thread]
BUG #18274: Error 'invalid XML content'
2024-01-06 22:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-07 18:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-14 18:28 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-14 19:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-14 20:58 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-14 23:34 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-15 03:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-15 04:18 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-15 15:47 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-16 09:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-16 13:55 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-16 23:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-25 04:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-25 12:12 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-26 01:24 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18274: Error 'invalid XML content'
2024-01-26 04:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
[16+ messages in thread]
Last update of python3-psycopg2 breaks RHEL-8
2024-01-25 07:14 UTC Frank Büttner <frank.buettner@mdc-berlin.de>
` Re: Last update of python3-psycopg2 breaks RHEL-8
2024-01-25 14:47 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #18311: python3-psycopg2 packaged for wrong python version
2024-01-25 09:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18311: python3-psycopg2 packaged for wrong python version
2024-01-25 14:47 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
回复: [External]Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
2024-01-25 04:01 UTC Jason ChenTJ (CN) <Jason.ChenTJ@homecredit.cn>
` 回复: [External]Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
2024-01-25 04:55 UTC Jason ChenTJ (CN) <Jason.ChenTJ@homecredit.cn>
` 回复: [External]Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
2024-01-25 06:33 UTC Jason ChenTJ (CN) <Jason.ChenTJ@homecredit.cn>
` Re: 回复: [External]Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
2024-01-25 07:10 UTC Michael Paquier <michael@paquier.xyz>
` Re: 回复: [External]Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
2024-01-25 14:06 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[5+ messages in thread]
BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
2024-01-24 06:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
2024-01-24 15:32 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: [External]Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment
2024-01-25 06:24 UTC jian he <jian.universality@gmail.com>
[3+ messages in thread]
BUG #18307: system columns does not support using join
2024-01-24 04:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18307: system columns does not support using join
2024-01-24 14:26 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18307: system columns does not support using join
2024-01-25 03:33 UTC RekGRpth <rekgrpth@gmail.com>
` Re: BUG #18307: system columns does not support using join
2024-01-25 03:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure
2024-01-24 12:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure
2024-01-24 15:24 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure
2024-01-24 16:00 UTC Alexander Lakhin <exclusion@gmail.com>
[3+ messages in thread]
BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-16 04:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-17 07:48 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-17 11:54 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-17 15:03 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-18 09:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-18 15:42 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-19 09:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-22 10:36 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-22 17:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-23 03:19 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-24 06:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18297: Error when adding a column to a parent table with complex inheritance
2024-01-24 06:20 UTC Michael Paquier <michael@paquier.xyz>
[12+ messages in thread]
BUG #18306: Slow SQL query Postgresql 15 Debian family linux.
2024-01-23 12:45 UTC PG Bug reporting form <noreply@postgresql.org>
Removing const-false IS NULL quals and redundant IS NOT NULL quals
2023-12-07 11:04 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Removing const-false IS NULL quals and redundant IS NOT NULL quals
2023-12-27 11:20 UTC Andy Fan <zhihuifan1213@163.com>
` Re: Removing const-false IS NULL quals and redundant IS NOT NULL quals
2023-12-27 11:58 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Removing const-false IS NULL quals and redundant IS NOT NULL quals
2023-12-29 01:25 UTC Andy Fan <zhihuifan1213@163.com>
` Re: Removing const-false IS NULL quals and redundant IS NOT NULL quals
2024-01-22 04:31 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Removing const-false IS NULL quals and redundant IS NOT NULL quals
2024-01-22 11:01 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Removing const-false IS NULL quals and redundant IS NOT NULL quals
2024-01-22 11:11 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Removing const-false IS NULL quals and redundant IS NOT NULL quals
2024-01-23 05:10 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Removing const-false IS NULL quals and redundant IS NOT NULL quals
2024-01-23 06:16 UTC Richard Guo <guofenglinux@gmail.com>
[9+ messages in thread]
Re: MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit
2024-01-22 15:27 UTC feichanghong <feichanghong@qq.com>
BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-12 17:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-13 04:33 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-15 15:23 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-16 15:59 UTC Jeremy Schneider <schneider@ardentperf.com>
` RE: [EXTERNAL] Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-16 17:42 UTC Fensterman, John P <John.Fensterman@charter.com>
` RE: [EXTERNAL] Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-18 21:13 UTC Fensterman, John P <John.Fensterman@charter.com>
` RE: [EXTERNAL] Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-18 21:15 UTC Fensterman, John P <John.Fensterman@charter.com>
` Re: [EXTERNAL] Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-18 23:57 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-18 23:59 UTC Devrim Gündüz <devrim@gunduz.org>
` RE: [EXTERNAL] Re: BUG #18289: postgresql14-devel-14.10-2PGDG.rhel8.x86_64.rpm Contains invalid cLang option in Makefile.global
2024-01-22 15:07 UTC Fensterman, John P <John.Fensterman@charter.com>
[10+ messages in thread]
Postgres 16.1 - Bug: cache entry already complete
2024-01-02 15:36 UTC Amadeo Gallardo <amadeo@ruddr.io>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-02 17:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-02 19:51 UTC Amadeo Gallardo <amadeo@ruddr.io>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-02 23:48 UTC Amadeo Gallardo <amadeo@ruddr.io>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-02 23:59 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-03 00:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-03 00:40 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-03 01:47 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-03 02:36 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-03 03:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-03 11:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-04 12:04 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-11 03:26 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Postgres 16.1 - Bug: cache entry already complete
2024-01-22 09:49 UTC David Rowley <dgrowleyml@gmail.com>
[14+ messages in thread]
Excessive number of replication slots for 12->14 logical replication
2022-07-14 11:51 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-15 04:55 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-15 07:45 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-15 22:14 UTC Andres Freund <andres@anarazel.de>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-18 03:37 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-18 03:51 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-18 08:09 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-18 09:43 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-18 11:20 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-24 08:16 UTC Ajin Cherian <itsajin@gmail.com>
` RE: Excessive number of replication slots for 12->14 logical replication
2022-07-25 09:48 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-25 11:43 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-28 01:55 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-29 07:05 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-29 09:36 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-07-29 11:35 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-01 01:50 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-01 06:45 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-02 01:54 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-04 07:41 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-04 12:47 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-05 00:47 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-11 15:04 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-12 01:28 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-12 03:44 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-12 05:21 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-12 05:42 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-16 11:36 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-17 08:06 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-17 09:47 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-18 00:50 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-18 02:37 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-18 02:39 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-18 03:44 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-18 05:45 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-18 05:58 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-18 10:30 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-18 13:29 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-23 14:26 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-24 01:08 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-24 05:54 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-25 14:07 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-26 01:34 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-30 06:44 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-08-30 09:01 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-09-09 21:48 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Excessive number of replication slots for 12->14 logical replication
2022-09-10 03:41 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-09-10 05:36 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-09-10 06:15 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-09-10 10:22 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Excessive number of replication slots for 12->14 logical replication
2022-09-10 10:34 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` RE: Excessive number of replication slots for 12->14 logical replication
2022-09-11 14:55 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-09-12 04:51 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-09-12 06:15 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Excessive number of replication slots for 12->14 logical replication
2022-09-12 06:51 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-09-12 06:55 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2022-09-12 10:37 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2024-01-18 07:29 UTC Bowen Shi <zxwsbg12138@gmail.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2024-01-19 16:40 UTC vignesh C <vignesh21@gmail.com>
` RE: Excessive number of replication slots for 12->14 logical replication
2024-01-21 13:32 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: Excessive number of replication slots for 12->14 logical replication
2024-01-22 02:26 UTC Bowen Shi <zxwsbg12138@gmail.com>
[61+ 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