pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-12 08:31 UTC Mareks Kalnaès <Mareks.Kalnacs@datakom.lv>
` Re: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-12 12:31 UTC Victor Yegorov <vyegorov@gmail.com>
` Re: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-12 12:43 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-12 13:16 UTC Mareks Kalnačs <Mareks.Kalnacs@datakom.lv>
` RE: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-12 16:23 UTC Mareks Kalnačs <Mareks.Kalnacs@datakom.lv>
` Re: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-12 16:43 UTC Victor Yegorov <vyegorov@gmail.com>
` Re: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-12 17:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-12 17:14 UTC Adrien Nayrat <adrien.nayrat@anayrat.info>
` RE: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-13 10:03 UTC Mareks Kalnačs <Mareks.Kalnacs@datakom.lv>
` RE: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-13 10:19 UTC Mareks Kalnaès <Mareks.Kalnacs@datakom.lv>
` Re: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-13 17:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: PostgreSQL 10.0 SELECT LIMIT performance problem
2018-09-14 05:59 UTC Mareks Kalnaès <Mareks.Kalnacs@datakom.lv>
` [PATCH v1 1/1] Fix unrecognized node type about statistics on expressions
2022-08-04 14:46 UTC Japin Li <japinli@hotmail.com>
[13+ messages in thread]
BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas
2022-08-03 10:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas
2022-08-03 11:13 UTC Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
` Re: BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas
2022-08-03 19:17 UTC Poornima Venkatesan <poornima3230@gmail.com>
` Re: BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas
2022-08-04 08:32 UTC Mateusz Henicz <mateuszhenicz@gmail.com>
[4+ messages in thread]
BUG #17569: false negative / positive results when using <-> (followed by) and tsvector limit (16383) hit
2022-08-03 17:51 UTC PG Bug reporting form <noreply@postgresql.org>
Statistics updates is delayed when using `commit and chain`
2021-07-09 09:05 UTC Lætitia Avrot <laetitia.avrot@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-09 11:02 UTC Japin Li <japinli@hotmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-09 11:15 UTC Japin Li <japinli@hotmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-09 12:25 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-10 02:31 UTC Japin Li <japinli@hotmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-12 12:56 UTC Lætitia Avrot <laetitia.avrot@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-12 13:34 UTC Japin Li <japinli@hotmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-12 14:08 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-12 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-13 13:33 UTC Lætitia Avrot <laetitia.avrot@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-14 01:55 UTC Japin Li <japinli@hotmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-14 03:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-14 03:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-14 03:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-14 04:02 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-14 04:06 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-14 06:53 UTC Japin Li <japinli@hotmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-26 15:53 UTC Lætitia Avrot <laetitia.avrot@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2021-07-27 02:28 UTC Japin Li <japinli@hotmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2022-05-14 15:11 UTC Laetitia Avrot <laetitia.avrot@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2022-07-28 21:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Statistics updates is delayed when using `commit and chain`
2022-08-01 08:13 UTC Laetitia Avrot <laetitia.avrot@gmail.com>
` Re: Statistics updates is delayed when using `commit and chain`
2022-08-01 16:12 UTC Andres Freund <andres@anarazel.de>
` Re: Statistics updates is delayed when using `commit and chain`
2022-08-01 16:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Statistics updates is delayed when using `commit and chain`
2022-08-01 16:40 UTC Andres Freund <andres@anarazel.de>
` Re: Statistics updates is delayed when using `commit and chain`
2022-08-01 16:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Statistics updates is delayed when using `commit and chain`
2022-08-01 17:10 UTC Andres Freund <andres@anarazel.de>
` Re: Statistics updates is delayed when using `commit and chain`
2022-08-01 17:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Statistics updates is delayed when using `commit and chain`
2022-08-01 23:03 UTC Andres Freund <andres@anarazel.de>
[29+ messages in thread]
BUG #17565: Extended query protocol incorrectly sets TBLOCK_STARTED even though multiple queries can be executed
2022-08-01 20:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17565: Extended query protocol incorrectly sets TBLOCK_STARTED even though multiple queries can be executed
2022-08-01 22:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Re[2]: BUG #17561: Server crashes on executing row() with very long argument list
2022-08-01 07:17 UTC Егор Чиндяскин <kyzevan23@mail.ru>
` Re: Re[2]: BUG #17561: Server crashes on executing row() with very long argument list
2022-08-01 10:03 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Re[2]: BUG #17561: Server crashes on executing row() with very long argument list
2022-08-01 10:33 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Re[2]: BUG #17561: Server crashes on executing row() with very long argument list
2022-08-01 10:51 UTC Richard Guo <guofenglinux@gmail.com>
` Re: Re[2]: BUG #17561: Server crashes on executing row() with very long argument list
2022-08-01 14:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #17563: exception " Segmentation fault" occured when i executed 'reindex index concurrently' in pg12.0
2022-08-01 02:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17563: exception " Segmentation fault" occured when i executed 'reindex index concurrently' in pg12.0
2022-08-01 07:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17563: exception " Segmentation fault" occured when i executed 'reindex index concurrently' in pg12.0
2022-08-01 14:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17560: Planner can not find plan with lowest cost
2022-07-28 16:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17560: Planner can not find plan with lowest cost
2022-07-28 19:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17560: Planner can not find plan with lowest cost
2022-07-29 07:30 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #17560: Planner can not find plan with lowest cost
2022-07-29 10:30 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17560: Planner can not find plan with lowest cost
2022-08-01 09:06 UTC Stanisław Skonieczny <stanislaw.skonieczny@gmail.com>
[5+ messages in thread]
RFC 9266: Channel Bindings for TLS 1.3 support
2022-07-28 20:33 UTC * Neustradamus * <neustradamus@hotmail.com>
` Re: RFC 9266: Channel Bindings for TLS 1.3 support
2022-07-29 05:44 UTC Michael Paquier <michael@paquier.xyz>
` Re: RFC 9266: Channel Bindings for TLS 1.3 support
2022-07-29 17:28 UTC Jacob Champion <jchampion@timescale.com>
` Re: RFC 9266: Channel Bindings for TLS 1.3 support
2022-07-30 02:38 UTC Michael Paquier <michael@paquier.xyz>
[4+ messages in thread]
BUG #17562: Strange behavior of to_tsquery() with a - character
2022-07-29 22:18 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 09:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 09:56 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 10:14 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 10:58 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 13:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 14:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 15:47 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 16:24 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17561: Server crashes on executing row() with very long argument list
2022-07-29 16:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
xmin of slot is not moving | hot standby feedback sending old xmin.
2022-07-28 09:38 UTC Tushar Takate <tushar11.takate@gmail.com>
` Re: xmin of slot is not moving | hot standby feedback sending old xmin.
2022-07-28 09:52 UTC Andres Freund <andres@anarazel.de>
[2+ messages in thread]
Create temporary table in replica instances issues
2022-07-28 08:36 UTC Saravanan Shanmugam <saravanantvr1984@gmail.com>
` Re: Create temporary table in replica instances issues
2022-07-28 09:25 UTC Saravanan Shanmugam <saravanantvr1984@gmail.com>
` Re: Create temporary table in replica instances issues
2022-07-28 09:40 UTC Guillaume Lelarge <guillaume@lelarge.info>
[3+ messages in thread]
BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
2020-12-01 05:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
2020-12-01 20:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
2020-12-02 01:11 UTC Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi.shinoda@hpe.com>
` Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
2020-12-03 20:50 UTC Andres Freund <andres@anarazel.de>
` RE: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
2020-12-07 08:58 UTC Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi.shinoda@hpe.com>
` Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
2020-12-08 07:35 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
2022-07-28 04:11 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #16754: When using LLVM and parallel queries aborted all session by pg_cancel_backend.
2022-07-28 04:12 UTC Amit Langote <amitlangote09@gmail.com>
[8+ messages in thread]
"SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3?
2022-06-16 06:10 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3?
2022-07-01 09:49 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-22 07:56 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-22 19:07 UTC Bruce Momjian <bruce@momjian.us>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-22 19:43 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-22 21:08 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-22 21:17 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-23 15:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-24 07:55 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-25 06:04 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-25 13:39 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-26 12:40 UTC Marco Boeringa <marco@boeringa.demon.nl>
` Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
2022-07-27 07:53 UTC Marco Boeringa <marco@boeringa.demon.nl>
[13+ messages in thread]
BUG #17559: Inconsistent visibility in trigger function
2022-07-27 07:32 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17556: ts_headline does not correctly find matches when separated by 4,999 words
2022-07-22 14:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17556: ts_headline does not correctly find matches when separated by 4,999 words
2022-07-25 02:36 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17556: ts_headline does not correctly find matches when separated by 4,999 words
2022-07-25 13:31 UTC Alex Malek <magicagent@gmail.com>
[3+ messages in thread]
BUG #17557: ts_headline will error with "invalid memory alloc request size" for large documents
2022-07-22 15:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17557: ts_headline will error with "invalid memory alloc request size" for large documents
2022-07-23 14:33 UTC Japin Li <japinli@hotmail.com>
[2+ messages in thread]
If a row-level security policy contains a set returning function, pg_dump returns an incorrect serialization of that policy if the return type of the function was altered
2022-07-19 10:22 UTC Timo Stolz <timo.stolz@nullachtvierzehn.de>
` Re: If a row-level security policy contains a set returning function, pg_dump returns an incorrect serialization of that policy if the return type of the function was altered
2022-07-20 20:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: If a row-level security policy contains a set returning function, pg_dump returns an incorrect serialization of that policy if the return type of the function was altered
2022-07-21 07:19 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: If a row-level security policy contains a set returning function, pg_dump returns an incorrect serialization of that policy if the return type of the function was altered
2022-07-21 17:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: If a row-level security policy contains a set returning function, pg_dump returns an incorrect serialization of that policy if the return type of the function was altered
2022-07-21 19:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: If a row-level security policy contains a set returning function, pg_dump returns an incorrect serialization of that policy if the return type of the function was altered
2022-07-21 21:27 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: If a row-level security policy contains a set returning function, pg_dump returns an incorrect serialization of that policy if the return type of the function was altered
2022-07-22 16:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
BUG #17533: run benchmarksql test failed
2022-06-25 15:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #17533: run benchmarksql test failed
2022-07-22 09:24 UTC sean <zoulx1982@163.com>
[2+ messages in thread]
Trusted extension cannot be dropped by the owner of the extension
2021-05-20 22:54 UTC Harinath Kanchu <hkanchu@apple.com>
` Trusted extension cannot be dropped by the owner of the extension
2022-07-20 06:44 UTC Harinath Kanchu <hkanchu@apple.com>
` Re: Trusted extension cannot be dropped by the owner of the extension
2022-07-20 16:35 UTC Bruce Momjian <bruce@momjian.us>
[3+ messages in thread]
BUG #17555: Missing rhel-9 repo
2022-07-18 12:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17555: Missing rhel-9 repo
2022-07-19 09:00 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
[15] Custom WAL resource managers, single user mode, and recovery
2022-07-15 00:22 UTC Jeff Davis <pgsql@j-davis.com>
` Re: [15] Custom WAL resource managers, single user mode, and recovery
2022-07-15 00:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [15] Custom WAL resource managers, single user mode, and recovery
2022-07-15 03:32 UTC Andres Freund <andres@anarazel.de>
` Re: [15] Custom WAL resource managers, single user mode, and recovery
2022-07-15 03:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [15] Custom WAL resource managers, single user mode, and recovery
2022-07-15 03:58 UTC Andres Freund <andres@anarazel.de>
` Re: [15] Custom WAL resource managers, single user mode, and recovery
2022-07-15 07:00 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: [15] Custom WAL resource managers, single user mode, and recovery
2022-07-15 07:26 UTC Andres Freund <andres@anarazel.de>
` Re: [15] Custom WAL resource managers, single user mode, and recovery
2022-07-15 19:43 UTC Jeff Davis <pgsql@j-davis.com>
` Re: [15] Custom WAL resource managers, single user mode, and recovery
2022-07-19 03:26 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[9+ messages in thread]
BUG #17496: to_char function resets if interval exceeds 23 hours 59 minutes
2022-05-24 18:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17496: to_char function resets if interval exceeds 23 hours 59 minutes
2022-05-24 19:55 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #17496: to_char function resets if interval exceeds 23 hours 59 minutes
2022-05-24 20:11 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17496: to_char function resets if interval exceeds 23 hours 59 minutes
2022-07-14 21:57 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #17496: to_char function resets if interval exceeds 23 hours 59 minutes
2022-07-15 07:58 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17496: to_char function resets if interval exceeds 23 hours 59 minutes
2022-07-18 21:21 UTC Bruce Momjian <bruce@momjian.us>
[6+ messages in thread]
BUG #17554: when i use rule on table which have serial column, the nextval exec twice.
2022-07-18 09:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17554: when i use rule on table which have serial column, the nextval exec twice.
2022-07-18 10:42 UTC Francisco Olarte <folarte@peoplecall.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