Horton
Menu

Messages in pgsql-bugs

Same data as JSON: GET /api/v1/messages same messages as JSON; filter by `list`, `from`/`to`. API reference →
Date ▼ SubjectFrom
2025-05-19T07:24:47Z Re: BUG #18923: pg_dump 18beta1 fails to process complex table names Has attachments Stepan Neretin <slpmcf@gmail.com>
2025-05-19T07:15:56Z Re: Understanding JDBC Behaviour Laurenz Albe <laurenz.albe@cybertec.at>
2025-05-19T05:03:02Z Ge Yuxiang added you to the postgresql group Ge Yuxiang <Ge_Yuxiang@outlook.com>
2025-05-18T20:47:15Z Re: Incorrect calculation of path fraction value in MergeAppend Alexander Korotkov <aekorotkov@gmail.com>
2025-05-18T14:28:58Z Re: Incorrect calculation of path fraction value in MergeAppend Tom Lane <tgl@sss.pgh.pa.us>
2025-05-18T12:23:06Z Re: Incorrect calculation of path fraction value in MergeAppend Alvaro Herrera <alvherre@alvh.no-ip.org>
2025-05-18T11:03:49Z Re: Incorrect calculation of path fraction value in MergeAppend Has attachments Alexander Korotkov <aekorotkov@gmail.com>
2025-05-17T12:35:00Z Understanding JDBC Behaviour Manav Kumar <mkumar@yugabyte.com>
2025-05-16T14:50:42Z Re: BUG #18923: pg_dump 18beta1 fails to process complex table names jian he <jian.universality@gmail.com>
2025-05-16T12:51:43Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Tom Lane <tgl@sss.pgh.pa.us>
2025-05-16T08:10:38Z Re: Re: Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost 萧鸿骏 <23031212454@stu.xidian.edu.cn>
2025-05-16T06:15:48Z Re: Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost Dilip Kumar <dilipbalaut@gmail.com>
2025-05-15T19:03:21Z Re: BUG #18923: pg_dump 18beta1 fails to process complex table names Tom Lane <tgl@sss.pgh.pa.us>
2025-05-15T19:03:11Z Re: BUG #18923: pg_dump 18beta1 fails to process complex table names Corey Huinker <corey.huinker@gmail.com>
2025-05-15T18:12:41Z Re: BUG #18923: pg_dump 18beta1 fails to process complex table names Has attachments Nathan Bossart <nathandbossart@gmail.com>
2025-05-15T17:55:32Z [PATCH v4 1/1] pg_dump: fix quoting in fetchAttributeStats() Nathan Bossart <nathan@postgresql.org>
2025-05-15T17:55:32Z [PATCH v2 1/1] pg_dump: fix quoting in fetchAttributeStats() Nathan Bossart <nathan@postgresql.org>
2025-05-15T17:25:59Z PGXS does not properly uninstall documentation Has attachments "Karl O. Pinc" <kop@karlpinc.com>
2025-05-15T16:21:10Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Sajith Prabhakar Shetty <ssajith@blackduck.com>
2025-05-15T15:46:31Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Tom Lane <tgl@sss.pgh.pa.us>
2025-05-15T15:28:44Z Re: BUG #18933: PostgreSQL fails to handle JOIN operation involving Empty Table Tom Lane <tgl@sss.pgh.pa.us>
2025-05-15T14:41:42Z Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error. Has attachments Heikki Linnakangas <hlinnaka@iki.fi>
2025-05-15T14:26:42Z Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 Andrei Lepikhov <lepihov@gmail.com>
2025-05-15T14:15:20Z Re: BUG #18930: PostgreSQL fails to handle INTERSECT operation involving Empty Table "David G. Johnston" <david.g.johnston@gmail.com>
2025-05-15T14:14:13Z Re: BUG #18932: PostgreSQL fails to handle EXCEPT operation when the left branch is an Empty Table "David G. Johnston" <david.g.johnston@gmail.com>