pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16837: Invalid memory access on \h in psql
  2021-01-26 07:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16837: Invalid memory access on \h in psql
  2021-01-26 11:17 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #16837: Invalid memory access on \h in psql
  2021-01-26 16:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16837: Invalid memory access on \h in psql
  2021-01-27 01:34 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
  [4+ messages in thread]

Assignment to composite type variable fails inside function but running query separately yields correct type & value ?
  2021-01-26 12:56 UTC  Tobias Gierke <tobias.gierke@code-sourcery.de>
` Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?
  2021-01-26 15:08 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?
  2021-01-26 15:19 UTC  Tobias Gierke <tobias.gierke@code-sourcery.de>
  [3+ messages in thread]

BUG #16836: performance drop while query information_schema since switch from postgres 10 to 12
  2021-01-25 08:39 UTC  PG Bug reporting form <noreply@postgresql.org>

(no subject)
  2021-01-25 05:46 UTC  Dhanraj Acharya <dhanraj.acharya@gmail.com>

BUG #16817: kill process cause postmaster hang
  2021-01-11 15:10 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16817: kill process cause postmaster hang
  2021-01-11 15:55 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16817: kill process cause postmaster hang
  2021-01-25 01:01 UTC  bchen90 <bchen90@163.com>
` Re: BUG #16817: kill process cause postmaster hang
  2021-01-25 01:29 UTC  Andy Fan <zhihui.fan1213@gmail.com>
` Re: BUG #16817: kill process cause postmaster hang
  2021-01-25 01:35 UTC  Michael Paquier <michael@paquier.xyz>
  [5+ messages in thread]

BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-15 07:48 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-16 21:15 UTC  Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
` RE: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-17 08:31 UTC  robionekenobi@bluewin.ch
` RE: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-17 18:22 UTC  robionekenobi@bluewin.ch
` Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-18 22:42 UTC  Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
` Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-19 05:23 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-19 08:31 UTC  Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
` Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-20 07:24 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-21 02:12 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-22 12:11 UTC  Jurko Gospodnetić <jurko.gospodnetic@pke.hr>
` Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment
  2021-01-23 04:49 UTC  Michael Paquier <michael@paquier.xyz>
  [11+ messages in thread]

BUG #16835: btree index does not work for where clause using 'foo%'
  2021-01-22 15:56 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16835: btree index does not work for where clause using 'foo%'
  2021-01-22 16:44 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXTERNAL] Re: BUG #16835: btree index does not work for where clause using 'foo%'
  2021-01-22 19:07 UTC  Zhang, Hongyan <ZhangH3@aetna.com>
` Re: [EXTERNAL] Re: BUG #16835: btree index does not work for where clause using 'foo%'
  2021-01-22 19:23 UTC  luis.roberto@siscobra.com.br
` Re: [EXTERNAL] Re: BUG #16835: btree index does not work for where clause using 'foo%'
  2021-01-22 19:45 UTC  Zhang, Hongyan <ZhangH3@aetna.com>
  [5+ messages in thread]

BUG #16832: Interrupted system call when working with large data tables
  2021-01-21 22:16 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16832: Interrupted system call when working with large data tables
  2021-01-22 17:24 UTC  Andres Freund <andres@anarazel.de>
  [2+ messages in thread]

BUG #16834: where-in: if the nested query fails, the parent query returns all the records
  2021-01-22 11:56 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records
  2021-01-22 14:38 UTC  Pantelis Theodosiou <ypercube@gmail.com>
` Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records
  2021-01-22 14:48 UTC  Pantelis Theodosiou <ypercube@gmail.com>
` Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records
  2021-01-22 15:19 UTC  Flavio Ricci <flavio.ricci82@gmail.com>
` Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records
  2021-01-22 15:27 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [5+ messages in thread]

segmentation fault in pg_restore with corrupt file
  2021-01-21 22:40 UTC  Jon Snell <jsnell@legalserver.org>

Problem with database
  2021-01-21 08:28 UTC  Ijas MP <ijasmp18@gmail.com>
` Re: Problem with database
  2021-01-21 16:39 UTC  Merlin Moncure <mmoncure@gmail.com>
  [2+ messages in thread]

BUG #16831: Idle postgres processes on Linux consumes huge amount of memory
  2021-01-20 21:04 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16831: Idle postgres processes on Linux consumes huge amount of memory
  2021-01-20 23:19 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` RE: BUG #16831: Idle postgres processes on Linux consumes huge amount of memory
  2021-01-21 15:40 UTC  Li, Yaqing <yaqing.li@rsa.com>
  [3+ messages in thread]

Проблемы с Postgresql 11
  2021-01-21 10:55 UTC  Сибиряков Евгений Олегович <atlant_it@mail.ru>
` Re: Проблемы с Postgresql 11
  2021-01-21 14:13 UTC  Sergey Mirvoda <sergey@mirvoda.com>
  [2+ messages in thread]

Reproducible GIST index corruption under concurrent updates
  2021-01-19 11:15 UTC  Duncan Sands <duncan.sands@deepbluecap.com>
` Re: Reproducible GIST index corruption under concurrent updates
  2021-01-19 17:12 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Reproducible GIST index corruption under concurrent updates
  2021-01-19 21:53 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Reproducible GIST index corruption under concurrent updates
  2021-01-19 22:31 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Reproducible GIST index corruption under concurrent updates
  2021-01-20 08:23 UTC  Duncan Sands <duncan.sands@deepbluecap.com>
` Re: Reproducible GIST index corruption under concurrent updates
  2021-01-20 10:04 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Reproducible GIST index corruption under concurrent updates
  2021-01-20 15:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Reproducible GIST index corruption under concurrent updates
  2021-01-20 22:26 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
  [8+ messages in thread]

Bug Report | Using ts_headline with the <-> operator
  2021-01-20 12:37 UTC  christian@games.no
` Re: Bug Report | Using ts_headline with the <-> operator
  2021-01-20 15:38 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #16830: Start of standby server never happens
  2021-01-19 15:08 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16829: Postgresql-12 service is not starting with SSL enabled in centos 7
  2021-01-18 18:05 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16829: Postgresql-12 service is not starting with SSL enabled in centos 7
  2021-01-18 22:51 UTC  Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
  [2+ messages in thread]

BUG #16822: Unable to launch setup
  2021-01-13 13:10 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16822: Unable to launch setup
  2021-01-18 05:13 UTC  Mihir Pandya <mihir.pandya@enterprisedb.com>
  [2+ messages in thread]

BUG #16823: Unreachable code
  2021-01-13 15:59 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16823: Unreachable code
  2021-01-13 16:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16823: Unreachable code
  2021-01-17 22:51 UTC  Rupert Gallagher <ruga@protonmail.com>
  [3+ messages in thread]

BUG #16828: duplicate results when using ** recursive expression in JSON path
  2021-01-17 10:34 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16828: duplicate results when using ** recursive expression in JSON path
  2021-01-17 19:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16828: duplicate results when using ** recursive expression in JSON path
  2021-01-17 21:24 UTC  Alexander Korotkov <aekorotkov@gmail.com>
  [3+ messages in thread]

syntactically correct query gives ERROR: failed to assign all NestLoopParams to plan nodes
  2021-01-15 19:54 UTC  Stephan Springl <springl-psql@bfw-online.de>
` Re: syntactically correct query gives ERROR: failed to assign all NestLoopParams to plan nodes
  2021-01-17 02:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #16824: Planner chooses poor path on query with Merge Join and pagination
  2021-01-13 22:13 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination
  2021-01-14 00:16 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination
  2021-01-16 22:34 UTC  Kisung Kim <kskim80@gmail.com>
` Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination
  2021-01-16 23:28 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

BUG #16826: Regex in substring(... from ..) wrong
  2021-01-15 08:23 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16826: Regex in substring(... from ..) wrong
  2021-01-15 14:20 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

BUG #16812: Logical decoding error
  2021-01-07 08:57 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16812: Logical decoding error
  2021-01-07 11:15 UTC  mayur <mayur555b@protonmail.com>
` Re: BUG #16812: Logical decoding error
  2021-01-12 05:08 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #16812: Logical decoding error
  2021-01-13 08:35 UTC  mayur <mayur555b@protonmail.com>
` Re: BUG #16812: Logical decoding error
  2021-01-15 03:59 UTC  Amit Kapila <amit.kapila16@gmail.com>
  [5+ messages in thread]

questions about porting postgresql to older operating system
  2021-01-14 16:39 UTC  Tim Kelly <gtkelly@dialectronics.com>
` Re: questions about porting postgresql to older operating system
  2021-01-14 18:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: questions about porting postgresql to older operating system
  2021-01-14 18:34 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: questions about porting postgresql to older operating system
  2021-01-14 18:44 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [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