Архив рассылок [pgsql-bugs]
BUG #16801: Invalid memory access on WITH RECURSIVE with nested WITHs PG Bug reporting form
how to prepare a create table statement Alexander Mills
Re: how to prepare a create table statement Pavel Stehule
Re: how to prepare a create table statement Michael Paquier
BUG #16803: create a table only one text/varchar column, storage options toast_tuple_target doesn't work PG Bug reporting form
BUG #16804: substring() function returns "negative substring length" error when using a large length argument PG Bug reporting form
Re: BUG #16774: PostgreSQL clean build MINGW64 gcc but initdb fails, cannot find startadress CreateProcessAsUserA Alexander Lakhin
Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument Pavel Stehule
Re: BUG #16804: substring() function returns "negative substring length" error when using a large length argument Jerry Sievert
BUG #16805: "ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... PRIMARY KEY" fails if column exists and is the primary PG Bug reporting form
compiling error on OpenWrt baych igor
compiling error on OpenWrt baych igor
BUG #16806: postgresql10 rpm is installed in the wrong directory PG Bug reporting form
Re: BUG #16805: "ALTER TABLE ... ADD COLUMN IF NOT EXISTS ... PRIMARY KEY" fails if column exists and is the primary Hamid Akhtar
Re: compiling error on OpenWrt Tom Lane
Re: compiling error on OpenWrt Michael Paquier
Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. Kasahara Tatsuhito
Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table Etsuro Fujita
BUG #16808: Postgres Windows installer fails with iso-8859-1 error and terminates PG Bug reporting form
BUG #16809: Package postgresql96-9.6.20-2PGDG.rhel7.x86_64 is not signed PG Bug reporting form
BUG #16811: Severe reproducible server backend crash PG Bug reporting form
AW: BUG #16806: postgresql10 rpm is installed in the wrong directory Kämpf, Heiko (OWL-IT)
BUG #16812: Logical decoding error PG Bug reporting form
AW: BUG #16806: postgresql10 rpm is installed in the wrong directory Kämpf, Heiko (OWL-IT)
BUG #16813: error to solve the problem "Windows could not stat file - over 4GB" PG Bug reporting form
BUG #16814: Invalid memory access on regexp_match with .* and BRE PG Bug reporting form
BUG #16815: Unable to use the X448 an X25519 elliptic curves. PG Bug reporting form
BUG #16816: Unexpected escaping of html output PG Bug reporting form
Re: BUG #16816: Unexpected escaping of html output Jeroen Baten
BUG #16817: kill process cause postmaster hang PG Bug reporting form
BUG #16818: progress reporting ALTER TABLE ADD UNIQUE PG Bug reporting form
Re: BUG #16818: progress reporting ALTER TABLE ADD UNIQUE Alvaro Herrera
Re: BUG #16812: Logical decoding error Amit Kapila
BUG #16819: Bug Installation PG Bug reporting form
Re: BUG #16808: Postgres Windows installer fails with iso-8859-1 error and terminates michael wilder
BUG #16820: PG will have a deadlock when multiple rows are updated concurrently PG Bug reporting form
NO acceptable C compiler found in the $PATH Nikhil Saple
BUG #16822: Unable to launch setup PG Bug reporting form
Re: NO acceptable C compiler found in the $PATH David G. Johnston
BUG #16823: Unreachable code PG Bug reporting form
Re: BUG #16823: Unreachable code Tom Lane
BUG #16824: Planner chooses poor path on query with Merge Join and pagination PG Bug reporting form
Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table Etsuro Fujita
Re: BUG #16807: Assert failed in postgres_fdw/estimate_path_cost_size with an empty foreign table Kyotaro Horiguchi
Re: questions about porting postgresql to older operating system Heikki Linnakangas
Re: BUG #16812: Logical decoding error Amit Kapila
BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment PG Bug reporting form
BUG #16826: Regex in substring(... from ..) wrong PG Bug reporting form
BUG #16827: macOS interrupted syscall leads to a crash PG Bug reporting form
Re: BUG #16826: Regex in substring(... from ..) wrong David G. Johnston
Re: BUG #16827: macOS interrupted syscall leads to a crash Ricardo Ungureanu
Re: syntactically correct query gives ERROR: failed to assign all NestLoopParams to plan nodes Tom Lane
BUG #16828: duplicate results when using ** recursive expression in JSON path PG Bug reporting form
Re: BUG #16828: duplicate results when using ** recursive expression in JSON path Alexander Korotkov
Re: BUG #16823: Unreachable code Rupert Gallagher
Re: BUG #16822: Unable to launch setup Mihir Pandya
BUG #16829: Postgresql-12 service is not starting with SSL enabled in centos 7 PG Bug reporting form
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Juan José Santamaría Flecha
Re: BUG #16829: Postgresql-12 service is not starting with SSL enabled in centos 7 Juan José Santamaría Flecha
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Juan José Santamaría Flecha
BUG #16830: Start of standby server never happens PG Bug reporting form
Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas
Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas
Bug in error reporting for multi-line JSON Simon Riggs
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier
Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas
BUG #16831: Idle postgres processes on Linux consumes huge amount of memory PG Bug reporting form
Re: Reproducible GIST index corruption under concurrent updates Heikki Linnakangas
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Michael Paquier
Problem with database Ijas MP
Проблемы с Postgresql 11 Сибиряков Евгений Олегович
Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. tomohiro hiramitsu
Re: Проблемы с Postgresql 11 Sergey Mirvoda
Re: Problem with database Merlin Moncure
BUG #16832: Interrupted system call when working with large data tables PG Bug reporting form
BUG #16833: postgresql 13.1 process crash every hour PG Bug reporting form
BUG #16834: where-in: if the nested query fails, the parent query returns all the records PG Bug reporting form
Re: BUG #16825: When building on Windows, cl /? retrun 'x64' not AMD64 and the build does not create x64 environment Jurko Gospodnetić
Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records Pantelis Theodosiou
Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records Pantelis Theodosiou
Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records Flavio Ricci
Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records David G. Johnston
BUG #16835: btree index does not work for where clause using 'foo%' PG Bug reporting form
Re: BUG #16833: postgresql 13.1 process crash every hour Andres Freund
Re: [EXTERNAL] Re: BUG #16835: btree index does not work for where clause using 'foo%' Zhang, Hongyan
Re: [EXTERNAL] Re: BUG #16835: btree index does not work for where clause using 'foo%' luis.roberto@siscobra.com.br
Re: BUG #16817: kill process cause postmaster hang Michael Paquier
BUG #16836: performance drop while query information_schema since switch from postgres 10 to 12 PG Bug reporting form
Re: Bug in error reporting for multi-line JSON Simon Riggs
BUG #16837: Invalid memory access on \h in psql PG Bug reporting form
Re: Bug in error reporting for multi-line JSON Hamid Akhtar
Re: BUG #16837: Invalid memory access on \h in psql Kyotaro Horiguchi
Assignment to composite type variable fails inside function but running query separately yields correct type & value ? Tobias Gierke
Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ? David G. Johnston
Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera
Re: BUG #16837: Invalid memory access on \h in psql Kyotaro Horiguchi
BUG #16838: notice is not displayed with in function PG Bug reporting form
BUG #16840: Rows not found in table partitioned by hash when not all partitions exists PG Bug reporting form
Re: Inconsistent application of [, ...] in documentation David G. Johnston
Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera
Re: Inconsistent application of [, ...] in documentation David G. Johnston
BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" PG Bug reporting form
Re: BUG #16840: Rows not found in table partitioned by hash when not all partitions exists Michał Albrycht
Re: BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" Sergei Kornilov
Re: BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" Ajay Chitale
Re: BUG #16838: notice is not displayed with in function Juan José Santamaría Flecha
Re: BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" Magnus Hagander
Re: BUG #16841: psql -- \d tablename , displays "Error : column c.relhasoids does not exit" Ajay Chitale
BUG #16842: pg_dump uses seek calls on pipe files: suggesting adding a flag to disable seek calls PG Bug reporting form
BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed PG Bug reporting form
BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data PG Bug reporting form
Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs Alvaro Herrera
Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data Kyotaro Horiguchi
Re: BUG #16844: Relation mapping file "global/pg_filenode.map" contains invalid data Peter Geoghegan
Use of HAVING (Select/Group By) on a output-name of an aggregate function causes SYNTAX ERROR Carlos Sotto Maior \(UOL\)