pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedHelp to Install Postgre SQL
2020-04-01 21:44 UTC Abdallah Farouk <abdallah-farouk@hotmail.com>
` Re: Help to Install Postgre SQL
2020-04-02 08:33 UTC Francisco Olarte <folarte@peoplecall.com>
` RE: Help to Install Postgre SQL
2020-04-02 08:52 UTC Abdallah Farouk <abdallah-farouk@hotmail.com>
` Re: Help to Install Postgre SQL
2020-04-02 09:26 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: Help to Install Postgre SQL
2020-04-04 03:33 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[5+ messages in thread]
BUG #16340: lo_manage() crashs DB instance
2020-04-03 13:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16340: lo_manage() crashs DB instance
2020-04-03 14:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16340: lo_manage() crashs DB instance
2020-04-03 15:02 UTC wcrowell <wcrowell@perforce.com>
[3+ messages in thread]
BUG #16339: [Errno 2] No such file or directory: 'python': 'python'
2020-04-03 11:56 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-12 20:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-12 20:55 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-12 21:01 UTC Mukesh Chhatani <chhatani.mukesh@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-12 21:41 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-13 06:58 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-13 10:39 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-13 10:49 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-13 18:37 UTC Mukesh Chhatani <chhatani.mukesh@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-13 18:42 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16109: Postgres planning time is high across version - 10.6 vs 10.10
2019-11-13 18:52 UTC Mukesh Chhatani <chhatani.mukesh@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-01-24 05:55 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-01-24 21:06 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-01-29 11:15 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-03-31 01:31 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-04-01 17:51 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-04-01 18:47 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-04-02 04:05 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-04-02 06:01 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-04-02 06:52 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
2020-04-03 02:31 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
[20+ messages in thread]
BUG #16338: casting interval '24h' to time returns '00:00:00' instead of '24:00:00'
2020-04-02 15:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16338: casting interval '24h' to time returns '00:00:00' instead of '24:00:00'
2020-04-02 16:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #16335: Installing plr12 fails due to package conflicts
2020-04-02 07:50 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #16331: segfault in checkpointer with full disk
2020-04-01 08:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16331: segfault in checkpointer with full disk
2020-04-01 09:04 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16331: segfault in checkpointer with full disk
2020-04-01 09:51 UTC Jozef Mlich <jmlich83@gmail.com>
` Re: BUG #16331: segfault in checkpointer with full disk
2020-04-01 17:25 UTC Julien Rouhaud <rjuju123@gmail.com>
[4+ messages in thread]
BUG #16332: The xmltable function returns 'comment()' as unusable xml appended together and having no xml tags
2020-04-01 15:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16332: The xmltable function returns 'comment()' as unusable xml appended together and having no xml tags
2020-04-01 16:12 UTC Pavel Stehule <pavel.stehule@gmail.com>
[2+ messages in thread]
BUG #16330: psql accesses null pointer in connect.c:do_connect
2020-03-30 02:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
2020-03-30 07:19 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
2020-03-30 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
2020-03-30 15:48 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
2020-03-31 07:21 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
2020-03-31 13:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
2020-03-31 13:52 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #16330: psql accesses null pointer in connect.c:do_connect
2020-04-01 06:07 UTC Michael Paquier <michael@paquier.xyz>
[8+ messages in thread]
BUG #16307: pgdg11-updates-debuginfo YUM repository missing RHEL releasever directories
2020-03-18 07:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16307: pgdg11-updates-debuginfo YUM repository missing RHEL releasever directories
2020-03-31 14:56 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-10 21:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-10 22:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-10 23:04 UTC Daniel WM <dwilches@gmail.com>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-14 20:43 UTC Daniel WM <dwilches@gmail.com>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-14 21:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-14 21:26 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-15 00:35 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-17 10:49 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-22 06:52 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-23 18:53 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-23 22:05 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-31 06:30 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
2020-03-31 09:37 UTC Amit Langote <amitlangote09@gmail.com>
[13+ messages in thread]
BUG #16327: Too many files in pg_replslot folder
2020-03-29 14:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16327: Too many files in pg_replslot folder
2020-03-29 19:52 UTC Euler Taveira <euler.taveira@2ndquadrant.com>
` Re: BUG #16327: Too many files in pg_replslot folder
2020-03-30 20:20 UTC Dmitry <romdn@inbox.ru>
[3+ messages in thread]
BUG #16321: Memory leaks in PostmasterMain
2020-03-27 03:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16321: Memory leaks in PostmasterMain
2020-03-27 14:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16321: Memory leaks in PostmasterMain
2020-03-30 02:10 UTC Hugh Wang <hghwng@gmail.com>
` Re: BUG #16321: Memory leaks in PostmasterMain
2020-03-30 11:13 UTC Francisco Olarte <folarte@peoplecall.com>
[4+ messages in thread]
BUG #16328: Generated column and inheritance: strange default error
2020-03-29 20:33 UTC PG Bug reporting form <noreply@postgresql.org>
apparent wraparound on postgresql 12
2020-03-29 01:49 UTC 56224665 <piikee@piikee.net>
BUG #16320: GSSAPI Error
2020-03-26 19:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16320: GSSAPI Error
2020-03-26 19:21 UTC Fahar Abbas <fahar.abbas@enterprisedb.com>
` Re: BUG #16320: GSSAPI Error
2020-03-27 16:30 UTC Stephen Frost <sfrost@snowman.net>
` Re: BUG #16320: GSSAPI Error
2020-03-27 19:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16320: GSSAPI Error
2020-03-27 19:57 UTC Stephen Frost <sfrost@snowman.net>
` Re: BUG #16320: GSSAPI Error
2020-03-27 20:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16320: GSSAPI Error
2020-03-27 21:08 UTC Stephen Frost <sfrost@snowman.net>
[7+ messages in thread]
BUG #16324: bad cost estimates for generic query plans
2020-03-27 15:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16324: bad cost estimates for generic query plans
2020-03-27 16:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16324: bad cost estimates for generic query plans
2020-03-27 17:16 UTC Todd A. Cook <ToddA.Cook@synopsys.com>
[3+ messages in thread]
BUG #16314: Database Cache Hit Ratio (Warning)
2020-03-24 12:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16314: Database Cache Hit Ratio (Warning)
2020-03-24 15:44 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #16314: Database Cache Hit Ratio (Warning)
2020-03-25 19:21 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16314: Database Cache Hit Ratio (Warning)
2020-03-26 13:51 UTC Rajiv Ranjan <rajiv.mca08@gmail.com>
` Re: BUG #16314: Database Cache Hit Ratio (Warning)
2020-03-26 15:40 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16314: Database Cache Hit Ratio (Warning)
2020-03-27 14:50 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
[6+ messages in thread]
BUG #16323: CREATE TABLE AS SELECT with unknown column type
2020-03-27 14:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16323: CREATE TABLE AS SELECT with unknown column type
2020-03-27 14:20 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
2020-03-25 11:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
2020-03-25 11:38 UTC hubert depesz lubaczewski <depesz@depesz.com>
` RE: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
2020-03-25 11:51 UTC Fan Liu <fan.liu@ericsson.com>
` RE: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
2020-03-25 12:26 UTC Fan Liu <fan.liu@ericsson.com>
` Re: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
2020-03-25 15:04 UTC hubert depesz lubaczewski <depesz@depesz.com>
` RE: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
2020-03-26 01:06 UTC Fan Liu <fan.liu@ericsson.com>
` RE: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
2020-03-26 11:11 UTC Fan Liu <fan.liu@ericsson.com>
[7+ messages in thread]
Negative cost is seen for plan node
2020-03-23 13:13 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Negative cost is seen for plan node
2020-03-24 04:00 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Negative cost is seen for plan node
2020-03-26 10:06 UTC Richard Guo <guofenglinux@gmail.com>
[3+ messages in thread]
BUG #16318: The default tablespace of a table and index is not inheriting the tablespace of database
2020-03-26 03:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16318: The default tablespace of a table and index is not inheriting the tablespace of database
2020-03-26 03:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #16318: The default tablespace of a table and index is not inheriting the tablespace of database
2020-03-26 06:51 UTC Jackey Lin <jackeylhm@gmail.com>
[3+ messages in thread]
BUG #16319: Changes in config files
2020-03-26 06:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16319: Changes in config files
2020-03-26 06:24 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
BUG #16315: Installing as SYSTEM generates error when icacls command runs
2020-03-24 15:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16315: Installing as SYSTEM generates error when icacls command runs
2020-03-26 05:48 UTC Fahar Abbas <fahar.abbas@enterprisedb.com>
[2+ messages in thread]
BUG #16316: The application has lost the database connection:
2020-03-24 17:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16316: The application has lost the database connection:
2020-03-25 19:27 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16316: The application has lost the database connection:
2020-03-25 20:58 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
[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