pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18934: Even with WITH ADMIN OPTION, I Cannot Manage Role Memberships
2025-05-19 08:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18934: Even with WITH ADMIN OPTION, I Cannot Manage Role Memberships
2025-05-20 06:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18934: Even with WITH ADMIN OPTION, I Cannot Manage Role Memberships
2025-05-26 09:18 UTC Luis Couto <snaperling@gmail.com>
` Re: BUG #18934: Even with WITH ADMIN OPTION, I Cannot Manage Role Memberships
2025-05-26 15:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18936: Trigger enable users to modify the tables which he doesn't have privilege
2025-05-20 13:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18936: Trigger enable users to modify the tables which he doesn't have privilege
2025-05-21 06:17 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18936: Trigger enable users to modify the tables which hedoesn't have privilege
2025-05-24 03:06 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #18936: Trigger enable users to modify the tables which hedoesn't have privilege
2025-05-24 05:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
Typo in the Timezone
2025-05-23 09:40 UTC Joseph Rana <josephranamgr7@gmail.com>
` Re: Typo in the Timezone
2025-05-23 10:38 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Typo in the Timezone
2025-05-23 14:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18931: Access to source rpms is not possible
2025-05-15 07:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18931: Access to source rpms is not possible
2025-05-21 15:53 UTC Magnus Hagander <magnus@hagander.net>
[2+ messages in thread]
BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-12 06:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-12 13:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-13 11:34 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-15 18:12 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-15 19:03 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-15 19:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-16 14:50 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-19 07:24 UTC Stepan Neretin <slpmcf@gmail.com>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-19 20:30 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
2025-05-20 21:33 UTC Nathan Bossart <nathandbossart@gmail.com>
[10+ messages in thread]
BUG #18929: After the view is created, executed query against the view definition, reported syntax error.
2025-05-15 04:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error.
2025-05-15 14:41 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error.
2025-05-19 15:52 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error.
2025-05-20 04:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error.
2025-05-20 05:02 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error.
2025-05-20 07:45 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18929: After the view is created, executed query against the view definition, reported syntax error.
2025-05-20 08:44 UTC Michael Paquier <michael@paquier.xyz>
[7+ messages in thread]
BUG #18935: The optimiser's choice of sort doubles the execution time.
2025-05-19 12:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18935: The optimiser's choice of sort doubles the execution time.
2025-05-19 15:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18935: The optimiser's choice of sort doubles the execution time.
2025-05-19 15:23 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18935: The optimiser's choice of sort doubles the execution time.
2025-05-19 15:47 UTC Alena Rybakina <a.rybakina@postgrespro.ru>
` Re: Re: BUG #18935: The optimiser's choice of sort doubles the execution time.
2025-05-20 03:28 UTC 萧鸿骏 <23031212454@stu.xidian.edu.cn>
[5+ messages in thread]
Understanding JDBC Behaviour
2025-05-17 12:35 UTC Manav Kumar <mkumar@yugabyte.com>
` Re: Understanding JDBC Behaviour
2025-05-19 07:15 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
Ge Yuxiang added you to the postgresql group
2025-05-19 05:03 UTC Ge Yuxiang <Ge_Yuxiang@outlook.com>
Incorrect calculation of path fraction value in MergeAppend
2025-04-29 11:14 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Incorrect calculation of path fraction value in MergeAppend
2025-05-07 15:35 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: Incorrect calculation of path fraction value in MergeAppend
2025-05-07 18:42 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Incorrect calculation of path fraction value in MergeAppend
2025-05-07 23:58 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: Incorrect calculation of path fraction value in MergeAppend
2025-05-18 11:03 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: Incorrect calculation of path fraction value in MergeAppend
2025-05-18 12:23 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Incorrect calculation of path fraction value in MergeAppend
2025-05-18 14:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Incorrect calculation of path fraction value in MergeAppend
2025-05-18 20:47 UTC Alexander Korotkov <aekorotkov@gmail.com>
[8+ messages in thread]
BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost
2025-05-14 08:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost
2025-05-14 08:23 UTC 萧鸿骏 <23031212454@stu.xidian.edu.cn>
` Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost
2025-05-15 08:45 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost
2025-05-15 09:15 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost
2025-05-15 13:12 UTC 萧鸿骏 <23031212454@stu.xidian.edu.cn>
` Re: Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost
2025-05-16 06:15 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: Re: Re: BUG #18927: Poor query plan - HashAggregate is more than twice as fast but at a higher cost
2025-05-16 08:10 UTC 萧鸿骏 <23031212454@stu.xidian.edu.cn>
[7+ messages in thread]
[PATCH v4 1/1] pg_dump: fix quoting in fetchAttributeStats()
2025-05-15 17:55 UTC Nathan Bossart <nathan@postgresql.org>
` [PATCH v2 1/1] pg_dump: fix quoting in fetchAttributeStats()
2025-05-15 17:55 UTC Nathan Bossart <nathan@postgresql.org>
[2+ messages in thread]
BUG #18933: PostgreSQL fails to handle JOIN operation involving Empty Table
2025-05-15 13:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18933: PostgreSQL fails to handle JOIN operation involving Empty Table
2025-05-15 15:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18930: PostgreSQL fails to handle INTERSECT operation involving Empty Table
2025-05-15 07:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18930: PostgreSQL fails to handle INTERSECT operation involving Empty Table
2025-05-15 14:15 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18932: PostgreSQL fails to handle EXCEPT operation when the left branch is an Empty Table
2025-05-15 13:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18932: PostgreSQL fails to handle EXCEPT operation when the left branch is an Empty Table
2025-05-15 14:14 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
pg16 ALTER ROLE [NO]INHERIT has no effect on existing grants
2025-05-14 20:27 UTC Jason Matthew <Jason.Matthew@sas.com>
` Re: pg16 ALTER ROLE [NO]INHERIT has no effect on existing grants
2025-05-14 21:16 UTC David G. Johnston <david.g.johnston@gmail.com>
` RE: pg16 ALTER ROLE [NO]INHERIT has no effect on existing grants
2025-05-15 00:57 UTC Jason Matthew <Jason.Matthew@sas.com>
[3+ messages in thread]
BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema
2025-05-14 12:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema
2025-05-14 15:06 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema
2025-05-14 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema
2025-05-14 16:30 UTC Jackie Li <jackie.space@gmail.com>
` Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer pool_mode=transaction using the wrong schema
2025-05-14 16:38 UTC Jackie Li <jackie.space@gmail.com>
[5+ messages in thread]
BUG #18926: PostgreSQL 17.5 produces malformed binary COPY output (`GPOCYP` instead of `PGCOPY`) across platform
2025-05-14 03:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18926: PostgreSQL 17.5 produces malformed binary COPY output (`GPOCYP` instead of `PGCOPY`) across platform
2025-05-14 12:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Unexpected output of PgRules
2025-05-14 09:14 UTC Manav Kumar <mkumar@yugabyte.com>
` Re: Unexpected output of PgRules
2025-05-14 10:40 UTC Manav Kumar <mkumar@yugabyte.com>
[2+ messages in thread]
reltuples decreasing with each autovacuum run
2025-02-12 11:19 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: reltuples decreasing with each autovacuum run
2025-05-02 06:16 UTC 濱中 弘和 <hamanaka7767.ita@al.asahi-life.co.jp>
` Re: reltuples decreasing with each autovacuum run
2025-05-12 09:01 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: reltuples decreasing with each autovacuum run
2025-05-14 01:28 UTC 濱中 弘和 <hamanaka7767.ita@al.asahi-life.co.jp>
[4+ messages in thread]
Re: Test mail for pgsql-hackers
2025-03-11 12:33 UTC BharatDB <bharatdbpg@gmail.com>
` Fwd: Test mail for pgsql-hackers
2025-03-11 12:37 UTC BharatDB <bharatdbpg@gmail.com>
` Re: Test mail for pgsql-hackers
2025-03-12 10:26 UTC Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
` Re: Test mail for pgsql-hackers
2025-03-12 12:28 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Test mail for pgsql-hackers
2025-05-13 13:40 UTC Andres Freund <andres@anarazel.de>
[5+ messages in thread]
Dependency on ccache in postgresql17-devel-17.5-1PGDG.rhel9
2025-05-12 06:18 UTC Zane Duffield <duffieldzane@gmail.com>
` Re: Dependency on ccache in postgresql17-devel-17.5-1PGDG.rhel9
2025-05-13 08:59 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: Dependency on ccache in postgresql17-devel-17.5-1PGDG.rhel9
2025-05-13 11:38 UTC Zane Duffield <duffieldzane@gmail.com>
[3+ messages in thread]
using CTE in multiple subqueries and full outer join - v15 vs v17 different query plan, v17 a bit slower than v15
2025-05-12 20:13 UTC marcos sicat <marcos.sicat@atlasifs.com>
Error while installing Postgres
2025-05-12 14:24 UTC arpana.thapa@agilent.com <arpana.thapa@agilent.com>
BUG #18924: The "ERROR: integer out of range" should be more detailed
2025-05-12 08:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18924: The "ERROR: integer out of range" should be more detailed
2025-05-12 12:36 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ 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