Архив рассылок [pgsql-bugs]
Doubt in reset date style Manav Kumar
Re: Doubt in reset date style David G. Johnston
Re: Doubt in reset date style Tom Lane
Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key Alvaro Herrera
BUG #18909: Query creates millions of temporary files and stalls PG Bug reporting form
Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error Tender Wang
Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error Alexander Lakhin
Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key Alvaro Herrera
Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key Alvaro Herrera
BUG #18910: DEREF_OF_NULL.RET Pointer, returned from function 'palloc0' at simplehash.h:1080, may be NULL PG Bug reporting form
BUG #18911: Bug in the command INHERITS. PG Bug reporting form
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load vignesh C
Re: BUG #18911: Bug in the command INHERITS. David G. Johnston
BUG #18912: TRAP: failed Assert("tag.spcOid != GLOBALTABLESPACE_OID"), File: "bufmgr.c", Line: 4165, PID: 2115 PG Bug reporting form
Re: BUG #18912: TRAP: failed Assert("tag.spcOid != GLOBALTABLESPACE_OID"), File: "bufmgr.c", Line: 4165, PID: 2115 Masahiko Sawada
Re: BUG #18911: Bug in the command INHERITS. David G. Johnston
BUG #18913: pgdg-redhat-repo-42.0-52PGDG.noarch: Cannot download, all mirrors were already tried without succes PG Bug reporting form
Re: BUG #18911: Bug in the command INHERITS. M. BROUSSE
BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false PG Bug reporting form
Re: BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false David Rowley
Re: BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false Daniel Gustafsson
BUG #18915: pgdg-redhat-repo-42.0-51PGDG.noarch package not available in postgres repo PG Bug reporting form
Re: BUG #18911: Bug in the command INHERITS. David G. Johnston
Re: BUG #18911: Bug in the command INHERITS. Álvaro Herrera
Re: BUG #18915: pgdg-redhat-repo-42.0-51PGDG.noarch package not available in postgres repo Devrim Gündüz
Re: Different behavior between v15 and v17 using WITH CTE David G. Johnston
BUG #18916: alter table ... set (n_distinct=) completely ignored on partition head and/or individual partitions PG Bug reporting form
Re: BUG #18916: alter table ... set (n_distinct=) completely ignored on partition head and/or individual partitions David Rowley
BUG #18917: "Foreign key constraint drop fails with 'column is not in index' unless pg_constraint is queried PG Bug reporting form
Re: BUG #18908: DEREF_OF_NULL: After having been assigned to a NULL value at descriptor.c:203 Robin Haberkorn
BUG #18918: cron.schedule_in_database ERROR: must be superuser to create a job for another role PG Bug reporting form
BUG #18919: Source archives in ftp/source/v17.5 are missing PG Bug reporting form
Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key Matthew Gabeler-Lee
Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key Matthew Gabeler-Lee
Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key Alvaro Herrera
Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key Alvaro Herrera
Re: BUG #18918: cron.schedule_in_database ERROR: must be superuser to create a job for another role David G. Johnston
BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 PG Bug reporting form
BUG #18923: pg_dump 18beta1 fails to process complex table names PG Bug reporting form
BUG #18924: The "ERROR: integer out of range" should be more detailed PG Bug reporting form
BUG #18925: Heap-buffer-overflow: pglz_compress with pglz_stategy_always PG Bug reporting form
BUG #18926: PostgreSQL 17.5 produces malformed binary COPY output (`GPOCYP` instead of `PGCOPY`) across platform PG Bug reporting form
Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load vignesh C
BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost PG Bug reporting form
Unexpected output of PgRules Manav Kumar
Re: Unexpected output of PgRules Manav Kumar
Re: pg16 ALTER ROLE [NO]INHERIT has no effect on existing grants David G. Johnston
BUG #18929: After the view is created, executed query against the view definition, reported syntax error. PG Bug reporting form
BUG #18930: PostgreSQL fails to handle INTERSECT operation involving Empty Table PG Bug reporting form
BUG #18931: Access to source rpms is not possible PG Bug reporting form
Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost Dilip Kumar
Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost Andrei Lepikhov
BUG #18932: PostgreSQL fails to handle EXCEPT operation when the left branch is an Empty Table PG Bug reporting form
Re: Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost 萧鸿骏
BUG #18933: PostgreSQL fails to handle JOIN operation involving Empty Table PG Bug reporting form
Re: BUG #18932: PostgreSQL fails to handle EXCEPT operation when the left branch is an Empty Table David G. Johnston
Understanding JDBC Behaviour Manav Kumar
Re: Incorrect calculation of path fraction value in MergeAppend Alexander Korotkov
Ge Yuxiang added you to the postgresql group Ge Yuxiang
Re: Understanding JDBC Behaviour Laurenz Albe
BUG #18934: Even with WITH ADMIN OPTION, I Cannot Manage Role Memberships PG Bug reporting form
Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Duncan Sands
BUG #18935: The optimiser's choice of sort doubles the execution time. PG Bug reporting form
Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error. Michael Paquier
Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error. Heikki Linnakangas
Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error. Michael Paquier
BUG #18936: Trigger enable users to modify the tables which he doesn't have privilege PG Bug reporting form
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Shlok Kyal
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
Re: BUG #18936: Trigger enable users to modify the tables which he doesn't have privilege Laurenz Albe
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Duncan Sands
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Duncan Sands
Re: BUG #18931: Access to source rpms is not possible Magnus Hagander
sudo dnf upgrade fails due to new llvm-libs-19.1.7-2.el9.x86_64 Michael.Arlt@universa.de
Re: Standby server with cascade logical replication could not be properly stopped under load Ajin Cherian
Re: Standby server with cascade logical replication could not be properly stopped under load shveta malik
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Shlok Kyal
Re: Standby server with cascade logical replication could not be properly stopped under load Bertrand Drouvot
Re: GSS Auth issue when user member of lots of AD groups Jacob Champion
Re: GSS Auth issue when user member of lots of AD groups Jacob Champion
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
Re: Typo in the Timezone Daniel Gustafsson
Re: Typo in the Timezone Tom Lane
Re: BUG #18936: Trigger enable users to modify the tables which hedoesn't have privilege Laurenz Albe
RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
BUG #18937: New error class 10 for XQuery errors lacks a "standard" error code PG Bug reporting form
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672" PG Bug reporting form
BUG #18939: GIN index not used when it's expected to be PG Bug reporting form
Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672" Masahiko Sawada
Re: [E] Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672" Amit Kapila
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
Re: Standby server with cascade logical replication could not be properly stopped under load Ajin Cherian
RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Hayato Kuroda (Fujitsu)
BUG #18940: PostgreSQL 18beta1 fails 'collate.windows.win1252' regression when building with MSYS/mingw PG Bug reporting form
Re: Standby server with cascade logical replication could not be properly stopped under load Michael Paquier
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada
BUG #18941: PostgreSQL planner does not select a multicolumn btree_gin index under RLS PG Bug reporting form
BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9 PG Bug reporting form
Re: BUG #18941: PostgreSQL planner does not select a multicolumn btree_gin index under RLS Pepe Fagoaga
Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Amit Kapila
[bug] keyword commit being accepted for column name Vinícius Abrahão
Re: [bug] keyword commit being accepted for column name David G. Johnston
