gmane.comp.db.postgresql.bugs archive

Re: Memory leak (possibly connected to postgis) leading to server crash

Tue, 17 Dec 2019 19:09:57 +0100

Tomas Vondra <[email protected]> • #53801

Re: BUG #16169: Default time output for 24:00 is 00:00

Tue, 17 Dec 2019 19:02:32 +0100

Francisco Olarte <[email protected]> • #53800

Re: BUG #16169: Default time output for 24:00 is 00:00

Tue, 17 Dec 2019 18:56:55 +0100

Tomas Vondra <[email protected]> • #53799

Re: BUG #16169: Default time output for 24:00 is 00:00

Tue, 17 Dec 2019 12:49:35 -0500

Tom Lane <[email protected]> • #53798

Re: BUG #16169: Default time output for 24:00 is 00:00

Tue, 17 Dec 2019 14:26:07 -0300

Alvaro Herrera <[email protected]> • #53797

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Tue, 17 Dec 2019 11:31:34 -0500

Tom Lane <[email protected]> • #53796

Re: ERROR: subtransaction logged without previous top-level txn record

Tue, 17 Dec 2019 18:15:42 +0300

Arseny Sher <[email protected]> • #53795

BUG #16170: pgadmin 4 won't even start

Tue, 17 Dec 2019 14:56:55 +0000

PG Bug reporting form <[email protected]> • #53794

Re: ERROR: subtransaction logged without previous top-level txn record

Tue, 17 Dec 2019 09:49:11 -0500

Dan Katz <[email protected]> • #53793

Re: Memory leak (possibly connected to postgis) leading to server crash

Tue, 17 Dec 2019 14:20:41 +0100

Roman Cervenak <[email protected]> • #53792

Re: Memory leak (possibly connected to postgis) leading to server crash

Tue, 17 Dec 2019 13:50:35 +0100

Tomas Vondra <[email protected]> • #53791

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Tue, 17 Dec 2019 13:07:51 +0100

Tomas Vondra <[email protected]> • #53790

Re: Memory leak (possibly connected to postgis) leading to server crash

Tue, 17 Dec 2019 12:51:27 +0100

Roman Cervenak <[email protected]> • #53789

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Tue, 17 Dec 2019 17:04:18 +0530

avinash varma <[email protected]> • #53788

BUG #16169: Default time output for 24:00 is 00:00

Tue, 17 Dec 2019 09:51:38 +0000

PG Bug reporting form <[email protected]> • #53787

Re: Reorderbuffer crash during recovery

Tue, 17 Dec 2019 14:32:10 +0530

Amit Kapila <[email protected]> • #53786

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Tue, 17 Dec 2019 07:46:46 +0100

Pavel Stehule <[email protected]> • #53785

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Tue, 17 Dec 2019 12:02:37 +0530

avinash varma <[email protected]> • #53784

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Tue, 17 Dec 2019 07:19:30 +0100

Pavel Stehule <[email protected]> • #53783

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Tue, 17 Dec 2019 11:41:22 +0530

avinash varma <[email protected]> • #53782

Re: Random crashes - segmentation fault

Tue, 17 Dec 2019 13:59:20 +0900

Michael Paquier <[email protected]> • #53781

Re: BUG #16161: pg_ctl stop fails sometimes (on Windows)

Tue, 17 Dec 2019 06:00:00 +0300

Alexander Lakhin <[email protected]> • #53780

Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash

Mon, 16 Dec 2019 22:02:49 +0100

Tomas Vondra <[email protected]> • #53779

Re: BUG #16161: pg_ctl stop fails sometimes (on Windows)

Mon, 16 Dec 2019 15:17:13 -0500

Tom Lane <[email protected]> • #53778

Re: Missing locales prevent autovacuum

Mon, 16 Dec 2019 16:19:11 -0300

Alvaro Herrera <[email protected]> • #53777

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Mon, 16 Dec 2019 22:00:00 +0300

Alexander Lakhin <[email protected]> • #53776

BUG #16168: Full text search parser prefers "file" over "asciiword"

Mon, 16 Dec 2019 18:22:33 +0000

PG Bug reporting form <[email protected]> • #53775

Missing locales prevent autovacuum

Mon, 16 Dec 2019 19:00:26 +0100

[email protected] • #53774

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Mon, 16 Dec 2019 11:16:54 -0500

Tom Lane <[email protected]> • #53773

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Mon, 16 Dec 2019 20:57:20 +0530

avinash varma <[email protected]> • #53772

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Mon, 16 Dec 2019 10:10:07 -0500

Tom Lane <[email protected]> • #53771

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Mon, 16 Dec 2019 20:00:39 +0530

avinash varma <[email protected]> • #53770

Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash

Mon, 16 Dec 2019 15:09:22 +0100

Tomas Vondra <[email protected]> • #53769

BUG #16167: frontend psql fails 'select * from table' if nrows * ncolumns = 2**32 in a table.

Mon, 16 Dec 2019 12:36:09 +0000

PG Bug reporting form <[email protected]> • #53768

Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Mon, 16 Dec 2019 14:23:58 +0200

Heikki Linnakangas <[email protected]> • #53767

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Mon, 16 Dec 2019 14:02:15 +0200

Heikki Linnakangas <[email protected]> • #53766

Planning time is high in Postgres 11.5 Compared with Postgres 10.11

Mon, 16 Dec 2019 14:28:11 +0530

avinash varma <[email protected]> • #53765

Re: BUG #16161: pg_ctl stop fails sometimes (on Windows)

Mon, 16 Dec 2019 08:00:00 +0300

Alexander Lakhin <[email protected]> • #53764

Re: BUG #16161: pg_ctl stop fails sometimes (on Windows)

Sun, 15 Dec 2019 16:26:40 -0500

Tom Lane <[email protected]> • #53763

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Sun, 15 Dec 2019 20:19:58 +0200

Heikki Linnakangas <[email protected]> • #53762

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Sun, 15 Dec 2019 12:57:37 -0500

Jeff Janes <[email protected]> • #53761

BUG #16166: Caution needs to be expanded

Sun, 15 Dec 2019 04:48:15 +0000

PG Bug reporting form <[email protected]> • #53760

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Sat, 14 Dec 2019 22:00:01 +0300

Alexander Lakhin <[email protected]> • #53759

Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash

Sat, 14 Dec 2019 14:39:12 +0100

Tomas Vondra <[email protected]> • #53758

Re: ANALYZE on parent table results in an error "tuple already updated by self"

Wed, 24 Jul 2019 09:17:36 +0200

Manuel Rigger <[email protected]> • #53757

Re: partition table slow planning

Wed, 24 Jul 2019 11:05:03 +0530

Dilip Kumar <[email protected]> • #53756

Re: BUG #16160: Minor memory leak in case of starting postgres server with SSL encryption

Sat, 14 Dec 2019 18:24:56 +0900

Michael Paquier <[email protected]> • #53755

Re: BUG #16165: Query Works fine but spam so many LOG: unrecognized win32 error code: 38

Sat, 14 Dec 2019 09:40:19 +0100

Juan José Santamaría Flecha <[email protected]> • #53754

Re: BUG #15899: Valgrind detects errors on create gist index

Wed, 10 Jul 2019 16:02:19 +0900

Michael Paquier <[email protected]> • #53753

Re: BUG #15901: Tablespace showing as null in psql and pgadmin

Tue, 9 Jul 2019 22:39:17 -0700

"David G. Johnston" <[email protected]> • #53752

Re: postgres has no spinlock support on riscv rv64imafdc

Fri, 13 Dec 2019 23:05:38 -0500

Tom Lane <[email protected]> • #53751

Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash

Sat, 14 Dec 2019 17:01:05 +1300

Thomas Munro <[email protected]> • #53750

BUG #16165: Query Works fine but spam so many LOG: unrecognized win32 error code: 38

Sat, 14 Dec 2019 03:44:37 +0000

PG Bug reporting form <[email protected]> • #53749

Re: postgres has no spinlock support on riscv rv64imafdc

Fri, 13 Dec 2019 21:26:17 -0600

Merlin Moncure <[email protected]> • #53748

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Fri, 13 Dec 2019 22:03:40 -0500

Jeff Janes <[email protected]> • #53747

Re: logical decoding bug: segfault in ReorderBufferToastReplace()

Fri, 13 Dec 2019 16:25:13 -0800

Andres Freund <[email protected]> • #53746

Re: BUG #16104: Invalid DSA Memory Alloc Request in Parallel Hash

Sat, 14 Dec 2019 13:22:39 +1300

Thomas Munro <[email protected]> • #53745

Re: logical decoding bug: segfault in ReorderBufferToastReplace()

Fri, 13 Dec 2019 16:13:35 -0800

Jeremy Schneider <[email protected]> • #53744

Re: Random crashes - segmentation fault

Fri, 13 Dec 2019 16:05:34 +0100

[email protected] (Kamil Jońca) • #53743

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Sat, 14 Dec 2019 00:02:52 +0200

Heikki Linnakangas <[email protected]> • #53742

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Fri, 13 Dec 2019 19:09:20 +0200

Heikki Linnakangas <[email protected]> • #53741

Re: Memory leak (possibly connected to postgis) leading to server crash

Fri, 13 Dec 2019 14:20:36 +0100

Tomas Vondra <[email protected]> • #53740

Re: Memory leak (possibly connected to postgis) leading to server crash

Fri, 13 Dec 2019 11:51:55 +0100

Roman Cervenak <[email protected]> • #53739

Re: FailedAssertion("!OidIsValid(def->collOid)", File: "view.c", Line: 89)

Fri, 13 Dec 2019 10:56:09 +0100

Manuel Rigger <[email protected]> • #53738

Re: BUG #16160: Minor memory leak in case of starting postgres server with SSL encryption

Fri, 13 Dec 2019 15:39:15 +0900

Michael Paquier <[email protected]> • #53737

Re: REINDEX CONCURRENTLY unexpectedly fails

Fri, 13 Dec 2019 12:45:36 +0900

Michael Paquier <[email protected]> • #53736

Re: REINDEX CONCURRENTLY unexpectedly fails

Fri, 13 Dec 2019 11:47:33 +0900

Michael Paquier <[email protected]> • #53735

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Fri, 13 Dec 2019 01:16:18 +0100

Tomas Vondra <[email protected]> • #53734

Re: ltrim function

Thu, 12 Dec 2019 19:08:04 -0500

Joe Conway <[email protected]> • #53733

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Thu, 12 Dec 2019 19:05:53 -0500

Jeff Janes <[email protected]> • #53732

ltrim function

Fri, 13 Dec 2019 02:15:33 +0300

Serdar Başyiğit <[email protected]> • #53731

Re: postgres has no spinlock support on riscv rv64imafdc

Thu, 12 Dec 2019 13:59:27 -0800

Andres Freund <[email protected]> • #53730

Re: REINDEX CONCURRENTLY unexpectedly fails

Thu, 12 Dec 2019 13:37:09 -0800

Andres Freund <[email protected]> • #53729

BUG #16164: Sending shared secret in all low case

Thu, 12 Dec 2019 20:15:22 +0000

PG Bug reporting form <[email protected]> • #53728

Re: REINDEX CONCURRENTLY unexpectedly fails

Thu, 12 Dec 2019 17:11:08 -0300

Alvaro Herrera <[email protected]> • #53727

Re: REINDEX CONCURRENTLY unexpectedly fails

Thu, 12 Dec 2019 11:55:06 -0800

Andres Freund <[email protected]> • #53726

BUG #16163: Seq scan through all the partitions on a partitioned table when joined small, dictionary table.

Thu, 12 Dec 2019 15:20:47 +0000

PG Bug reporting form <[email protected]> • #53725

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Thu, 12 Dec 2019 08:44:22 -0500

Tom Lane <[email protected]> • #53724

Re: BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting

Thu, 12 Dec 2019 09:52:29 -0300

Alvaro Herrera <[email protected]> • #53723

Re: BUG #16162: create index using gist_trgm_ops leads to panic

Thu, 12 Dec 2019 13:50:23 +0100

Tomas Vondra <[email protected]> • #53722

BUG #16162: create index using gist_trgm_ops leads to panic

Thu, 12 Dec 2019 10:22:21 +0000

PG Bug reporting form <[email protected]> • #53721

Re: BUG #16159: recovery requests WALs for the next timelines before timeline switch LSN has been reached

Thu, 12 Dec 2019 12:48:56 +0900 (JST)

Kyotaro Horiguchi <[email protected]> • #53720

Re: BUG #16161: pg_ctl stop fails sometimes (on Windows)

Wed, 11 Dec 2019 23:30:01 +0300

Alexander Lakhin <[email protected]> • #53719

BUG #16161: pg_ctl stop fails sometimes (on Windows)

Wed, 11 Dec 2019 20:00:02 +0000

PG Bug reporting form <[email protected]> • #53718

Re: logical replication: could not create file "state.tmp": File exists

Wed, 11 Dec 2019 09:40:11 -0800

Andres Freund <[email protected]> • #53717

Re: Memory leak (possibly connected to postgis) leading to server crash

Wed, 11 Dec 2019 18:23:39 +0100

Roman Cervenak <[email protected]> • #53716

Re: logical decoding bug: segfault in ReorderBufferToastReplace()

Wed, 11 Dec 2019 09:21:01 -0800

Andres Freund <[email protected]> • #53715

Re: logical decoding bug: segfault in ReorderBufferToastReplace()

Wed, 11 Dec 2019 12:12:48 -0500

Robert Haas <[email protected]> • #53714