pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedHow to prevent POSTGRES killing linux system from accepting too much inserts?
2019-12-18 09:53 UTC James(王旭) <wangxu@gu360.com>
` Re: How to prevent POSTGRES killing linux system from accepting too much inserts?
2019-12-18 18:07 UTC Steven Lembark <lembark@wrkhors.com>
` Re: How to prevent POSTGRES killing linux system from accepting too much inserts?
2019-12-18 18:34 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: How to prevent POSTGRES killing linux system from accepting too much inserts?
2019-12-18 19:09 UTC Jeff Janes <jeff.janes@gmail.com>
[4+ messages in thread]
weird long time query
2019-12-17 02:58 UTC Kaijiang Chen <chenkaijiang@gmail.com>
` Re: weird long time query
2019-12-17 11:08 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: weird long time query
2019-12-17 17:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: weird long time query
2019-12-18 03:23 UTC Kaijiang Chen <chenkaijiang@gmail.com>
` Fwd: weird long time query
2019-12-18 03:25 UTC Kaijiang Chen <chenkaijiang@gmail.com>
` Re: Fwd: weird long time query
2019-12-18 14:06 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Fwd: weird long time query
2019-12-18 16:14 UTC Kaijiang Chen <chenkaijiang@gmail.com>
` Re: Fwd: weird long time query
2019-12-18 16:23 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Fwd: weird long time query
2019-12-18 16:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
Memory leak (possibly connected to postgis) leading to server crash
2019-12-06 09:22 UTC Roman Cervenak <roman@cervenak.info>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-06 11:01 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-06 11:46 UTC Roman Cervenak <roman@cervenak.info>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-06 12:41 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-11 11:09 UTC Roman Cervenak <roman@cervenak.info>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-11 14:23 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-11 16:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-11 17:23 UTC Roman Cervenak <roman@cervenak.info>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-13 10:51 UTC Roman Cervenak <roman@cervenak.info>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-13 13:20 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-17 11:51 UTC Roman Cervenak <roman@cervenak.info>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-17 12:50 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-17 13:20 UTC Roman Cervenak <roman@cervenak.info>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-17 18:09 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-18 08:49 UTC Roman Cervenak <roman@cervenak.info>
` Re: Memory leak (possibly connected to postgis) leading to server crash
2019-12-18 14:55 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
[16+ messages in thread]
BUG #16163: Seq scan through all the partitions on a partitioned table when joined small, dictionary table.
2019-12-12 15:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16163: Seq scan through all the partitions on a partitioned table when joined small, dictionary table.
2019-12-18 01:34 UTC Amit Langote <amitlangote09@gmail.com>
[2+ messages in thread]
BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 09:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 17:26 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 17:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 17:56 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 18:02 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 18:14 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 18:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 18:29 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #16169: Default time output for 24:00 is 00:00
2019-12-17 21:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-16 08:58 UTC avinash varma <avinashvarma443@gmail.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-16 12:23 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-16 14:30 UTC avinash varma <avinashvarma443@gmail.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-16 15:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-16 15:27 UTC avinash varma <avinashvarma443@gmail.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-16 16:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-17 06:11 UTC avinash varma <avinashvarma443@gmail.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-17 06:19 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-17 06:32 UTC avinash varma <avinashvarma443@gmail.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-17 06:46 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-17 11:34 UTC avinash varma <avinashvarma443@gmail.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-17 12:07 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11
2019-12-17 16:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
[13+ messages in thread]
BUG #16170: pgadmin 4 won't even start
2019-12-17 14:56 UTC PG Bug reporting form <noreply@postgresql.org>
Random crashes - segmentation fault
2019-11-13 08:12 UTC kjonca@poczta.onet.pl
` Re: Random crashes - segmentation fault
2019-11-13 12:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: Random crashes - segmentation fault
2019-11-13 13:16 UTC kjonca@fastmail.com
` Re: Random crashes - segmentation fault
2019-11-13 15:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Random crashes - segmentation fault
2019-12-13 15:05 UTC kjonca@fastmail.com
` Re: Random crashes - segmentation fault
2019-12-17 04:59 UTC Michael Paquier <michael@paquier.xyz>
[6+ messages in thread]
Missing locales prevent autovacuum
2019-12-16 18:00 UTC Jens.Wilke@parcIT.de
` Re: Missing locales prevent autovacuum
2019-12-16 19:19 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
[2+ messages in thread]
BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-12 10:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-12 12:50 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-12 13:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-13 00:05 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-13 00:16 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-13 17:09 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-13 22:02 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-14 03:03 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-14 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-15 17:57 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-15 18:19 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-16 12:02 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #16162: create index using gist_trgm_ops leads to panic
2019-12-16 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
[13+ messages in thread]
BUG #16168: Full text search parser prefers "file" over "asciiword"
2019-12-16 18:22 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #16167: frontend psql fails 'select * from table' if nrows * ncolumns = 2**32 in a table.
2019-12-16 12:36 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #16166: Caution needs to be expanded
2019-12-15 04:48 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #16165: Query Works fine but spam so many LOG: unrecognized win32 error code: 38
2019-12-14 03:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16165: Query Works fine but spam so many LOG: unrecognized win32 error code: 38
2019-12-14 08:40 UTC Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
[2+ messages in thread]
ltrim function
2019-12-12 23:15 UTC Serdar Başyiğit <serdarbasyigit@yandex.com>
` Re: ltrim function
2019-12-13 00:08 UTC Joe Conway <mail@joeconway.com>
[2+ messages in thread]
BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting
2019-12-05 16:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting
2019-12-12 12:52 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
[2+ messages in thread]
Postgres 11.2 given error "Failed to initialize transaction_deferrable to 0"
2019-12-11 11:27 UTC Amul <amulpatel12345@gmail.com>
BUG #16152: postgresql10-plpython-10.11-2PGDG.rhel7.x86_64 requires an unexistant package
2019-12-05 12:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16152: postgresql10-plpython-10.11-2PGDG.rhel7.x86_64 requires an unexistant package
2019-12-11 09:07 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-06 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-06 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-06 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-06 15:40 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-07 12:35 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-07 16:00 UTC Alexander Law <exclusion@gmail.com>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-07 16:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-07 18:00 UTC Alexander Law <exclusion@gmail.com>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-07 19:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-07 21:00 UTC Alexander Law <exclusion@gmail.com>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-10 18:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16154: pg_ctl restart with a logfile fails sometimes (on Windows)
2019-12-11 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
[12+ messages in thread]
Warning in the RecordTransactionAbort routine during compilation with O3 flag
2019-12-09 03:49 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: Warning in the RecordTransactionAbort routine during compilation with O3 flag
2019-12-09 08:03 UTC Michael Paquier <michael@paquier.xyz>
` Re: Warning in the RecordTransactionAbort routine during compilation with O3 flag
2019-12-09 09:03 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: Warning in the RecordTransactionAbort routine during compilation with O3 flag
2019-12-10 03:13 UTC Michael Paquier <michael@paquier.xyz>
` Re: Warning in the RecordTransactionAbort routine during compilation with O3 flag
2019-12-10 07:18 UTC Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: Warning in the RecordTransactionAbort routine during compilation with O3 flag
2019-12-11 01:07 UTC Michael Paquier <michael@paquier.xyz>
[6+ messages in thread]
BUG #16158: Check constraints using SQL functions work incorrectly
2019-12-10 12:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16158: Check constraints using SQL functions work incorrectly
2019-12-10 15:00 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #16158: Check constraints using SQL functions work incorrectly
2019-12-10 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16158: Check constraints using SQL functions work incorrectly
2019-12-10 15:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Bug in pg_dump
2002-11-11 22:28 UTC Robert John Shepherd <robert@reviewer.co.uk>
` Re: Bug in pg_dump
2002-11-15 18:51 UTC Rod Taylor <rbt@rbt.ca>
` Re: Bug in pg_dump
2002-11-16 02:37 UTC Philip Warner <pjw@rhyme.com.au>
` Re: Bug in pg_dump
2002-11-16 11:54 UTC Robert John Shepherd <robert@reviewer.co.uk>
` Bug in pg_dump
2019-12-10 11:03 UTC Alejandro Meseguer <alex.meseguersilvestre@gmail.com>
[5+ messages in thread]
BUG #16157: handling of pg_malloc(0)
2019-12-09 12:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16157: handling of pg_malloc(0)
2019-12-09 15:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16157: handling of pg_malloc(0)
2019-12-10 09:51 UTC cilizili <cilizili@protonmail.com>
[3+ messages in thread]
BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers
2019-11-27 07:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers
2019-11-27 08:20 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers
2019-11-27 11:35 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers
2019-11-28 11:25 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers
2019-12-03 11:53 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers
2019-12-06 08:27 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers
2019-12-10 09:33 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[7+ messages in thread]
Unexpected extra row from jsonb_path_query() with a recursive path
2019-12-08 11:43 UTC Jan Przemysław Wójcik <jan.przemyslaw.wojcik@gmail.com>
` Re: Unexpected extra row from jsonb_path_query() with a recursive path
2019-12-09 07:28 UTC Michael Paquier <michael@paquier.xyz>
` Re: Unexpected extra row from jsonb_path_query() with a recursive path
2019-12-09 08:37 UTC Jan Przemysław Wójcik <jan.przemyslaw.wojcik@gmail.com>
` Re: Unexpected extra row from jsonb_path_query() with a recursive path
2019-12-10 02:38 UTC Michael Paquier <michael@paquier.xyz>
[4+ 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