pgsql-hackers  

Messages by Thread

• • Re: Improve LWLock tranche name visibility across backends Nathan Bossart
  • Re: Improve LWLock tranche name visibility across backends Sami Imseih
  • Re: Improve LWLock tranche name visibility across backends Sami Imseih
  • Re: Improve LWLock tranche name visibility across backends Nathan Bossart
  • Re: Improve LWLock tranche name visibility across backends Sami Imseih
  • Re: Improve LWLock tranche name visibility across backends Bertrand Drouvot
  • Re: Improve LWLock tranche name visibility across backends Sami Imseih
  • Re: Improve LWLock tranche name visibility across backends Sami Imseih
  • Re: Improve LWLock tranche name visibility across backends Sami Imseih
• redis_fdw failure on crake Richard Guo
  • Re: redis_fdw failure on crake Michael Paquier
  • Re: redis_fdw failure on crake Andrew Dunstan
  • Re: redis_fdw failure on crake Michael Paquier
• Re: Reduce "Var IS [NOT] NULL" quals during constant folding Richard Guo
  • Re: Reduce "Var IS [NOT] NULL" quals during constant folding Tomas Vondra
  • Re: Reduce "Var IS [NOT] NULL" quals during constant folding Richard Guo
  • Re: Reduce "Var IS [NOT] NULL" quals during constant folding Richard Guo
  • Re: Reduce "Var IS [NOT] NULL" quals during constant folding Nathan Bossart
  • Re: Reduce "Var IS [NOT] NULL" quals during constant folding Richard Guo
  • Re: Reduce "Var IS [NOT] NULL" quals during constant folding Nathan Bossart
  • Re: Reduce "Var IS [NOT] NULL" quals during constant folding Richard Guo
• Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions jian he
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Vik Fearing
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions jian he
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Vik Fearing
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Vik Fearing
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions jian he
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Vik Fearing
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Corey Huinker
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions jian he
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions jian he
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Corey Huinker
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions jian he
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Corey Huinker
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions jian he
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Vik Fearing
  • Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions Corey Huinker
• Re: Support tid range scan in parallel? David Rowley
  • Re: Support tid range scan in parallel? Cary Huang
  • Re: Support tid range scan in parallel? David Rowley
  • Re: Support tid range scan in parallel? Cary Huang
  • Re: Support tid range scan in parallel? David Rowley
• Re: teach pg_upgrade to handle in-place tablespaces Corey Huinker
  • Re: teach pg_upgrade to handle in-place tablespaces Nathan Bossart
  • Re: teach pg_upgrade to handle in-place tablespaces Michael Paquier
  • Re: teach pg_upgrade to handle in-place tablespaces Nathan Bossart
  • Re: teach pg_upgrade to handle in-place tablespaces Michael Paquier
  • Re: teach pg_upgrade to handle in-place tablespaces Nathan Bossart
  • Re: teach pg_upgrade to handle in-place tablespaces Nathan Bossart
• Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Nathan Bossart
  • Re: Non-reproducible AIO failure Alexander Lakhin
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Nico Williams
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Konstantin Knizhnik
  • Re: Non-reproducible AIO failure Ken Marshall
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Andres Freund
  • Re: Non-reproducible AIO failure Thomas Munro
  • Re: Non-reproducible AIO failure Andres Freund
• Re: [PATCH] Check for TupleTableSlot nullness before dereferencing Jacob Champion
  • Re: [PATCH] Check for TupleTableSlot nullness before dereferencing David Rowley
• Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment David Rowley
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Andrei Lepikhov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment David Rowley
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Andrei Lepikhov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Ilia Evdokimov
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment David Rowley
  • Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment Lukas Fittl
• Re: pgsql: Introduce pg_shmem_allocations_numa view Christoph Berg
  • Re: pgsql: Introduce pg_shmem_allocations_numa view Bertrand Drouvot
• Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Noah Misch
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Noah Misch
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Tom Lane
  • Re: Non-text mode for pg_dumpall Noah Misch
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Noah Misch
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Christoph Berg
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Christoph Berg
  • Re: Non-text mode for pg_dumpall Nathan Bossart
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Noah Misch
  • Re: Non-text mode for pg_dumpall Andrew Dunstan
  • Re: Non-text mode for pg_dumpall Noah Misch
  • Re: Non-text mode for pg_dumpall Robert Haas
• Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Nathan Bossart
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Nathan Bossart
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Michael Paquier
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Nathan Bossart
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Michael Paquier
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Bertrand Drouvot
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Bertrand Drouvot
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Nathan Bossart
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Michael Paquier
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Bertrand Drouvot
  • Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt Nathan Bossart
• Re: display hot standby state in psql prompt Greg Sabino Mullane
  • Re: display hot standby state in psql prompt Jim Jones
  • Re: display hot standby state in psql prompt Srinath Reddy Sadipiralla
  • Re: display hot standby state in psql prompt Jim Jones
  • Re: display hot standby state in psql prompt Srinath Reddy Sadipiralla
• Re: Exposing some hidden serializable transaction costs Greg Sabino Mullane
• Re: [PATCH] Generate random dates/times in a specified range Greg Sabino Mullane
  • Re: [PATCH] Generate random dates/times in a specified range Damien Clochard
  • Re: [PATCH] Generate random dates/times in a specified range Vik Fearing
  • Re: [PATCH] Generate random dates/times in a specified range Damien Clochard
  • Re: [PATCH] Generate random dates/times in a specified range Greg Sabino Mullane
  • Re: [PATCH] Generate random dates/times in a specified range Damien Clochard
  • Re: [PATCH] Generate random dates/times in a specified range Dean Rasheed
• Question on any plans to use the User Server/User Mapping to provide Logical Replication Subscriptions the user/password in an encrypted manner Vitale, Anthony, Sony Music
  • Re: Question on any plans to use the User Server/User Mapping to provide Logical Replication Subscriptions the user/password in an encrypted manner Amit Kapila
  • RE: Question on any plans to use the User Server/User Mapping to provide Logical Replication Subscriptions the user/password in an encrypted manner Vitale, Anthony, Sony Music
  • Re: Question on any plans to use the User Server/User Mapping to provide Logical Replication Subscriptions the user/password in an encrypted manner Amit Kapila
• Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Greg Burd
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Andres Freund
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Greg Burd
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Greg Burd
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Greg Burd
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Greg Burd
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Thomas Munro
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Thomas Munro
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Thomas Munro
  • Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock Greg Burd
• Update Examples in Logical Replication Docs Shlok Kyal
  • Re: Update Examples in Logical Replication Docs Peter Smith
  • Re: Update Examples in Logical Replication Docs Amit Kapila
• Re: Optimize shared LWLock acquisition for high-core-count systems Zhou, Zhiguo
• Re: Issues with hash and GiST LP_DEAD setting for kill_prior_tuple Peter Geoghegan
  • Re: Issues with hash and GiST LP_DEAD setting for kill_prior_tuple Amit Kapila
• Fwd: [PATCH] Support for basic ALTER TABLE progress reporting. Jiří Kavalík
  • Re: Fwd: [PATCH] Support for basic ALTER TABLE progress reporting. Álvaro Herrera
• Re: IPC/MultixactCreation on the Standby server Andrey Borodin
  • Re: IPC/MultixactCreation on the Standby server Andrey Borodin
  • Re: IPC/MultixactCreation on the Standby server Álvaro Herrera
  • Re: IPC/MultixactCreation on the Standby server Andrey Borodin
  • Re: IPC/MultixactCreation on the Standby server Andrey Borodin
  • Re: IPC/MultixactCreation on the Standby server Dmitry
  • Re: IPC/MultixactCreation on the Standby server Dmitry
  • Re: IPC/MultixactCreation on the Standby server Andrey Borodin
  • Re: IPC/MultixactCreation on the Standby server Andrey Borodin
  • Re: IPC/MultixactCreation on the Standby server Dmitry
  • Re: IPC/MultixactCreation on the Standby server Kirill Reshke
• Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Tom Lane
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Tom Lane
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Tom Lane
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Andrei Lepikhov
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih
  • Re: track generic and custom plans in pg_stat_statements Michael Paquier
  • Re: track generic and custom plans in pg_stat_statements Sami Imseih

• Earlier messages
• Later messages