pgsql-hackers  

Messages by Thread

• • Re: 10% drop in code line count in PG 17 Bruce Momjian
  • Re: 10% drop in code line count in PG 17 David Rowley
  • Re: 10% drop in code line count in PG 17 Bruce Momjian
  • Re: 10% drop in code line count in PG 17 David Rowley
  • Re: 10% drop in code line count in PG 17 Álvaro Herrera
  • Re: 10% drop in code line count in PG 17 Daniel Gustafsson
  • Re: 10% drop in code line count in PG 17 Bruce Momjian
  • Re: 10% drop in code line count in PG 17 Daniel Gustafsson
  • Re: 10% drop in code line count in PG 17 Bruce Momjian
  • Re: 10% drop in code line count in PG 17 Aleksander Alekseev
  • Re: 10% drop in code line count in PG 17 Peter Eisentraut
  • Re: 10% drop in code line count in PG 17 Bruce Momjian
  • Re: 10% drop in code line count in PG 17 Aleksander Alekseev
  • Re: 10% drop in code line count in PG 17 Aleksander Alekseev
  • Re: 10% drop in code line count in PG 17 Bruce Momjian
• Re: Make PGOAUTHCAFILE in libpq-oauth work out of debug mode Jacob Champion
  • Re: Make PGOAUTHCAFILE in libpq-oauth work out of debug mode Jacob Champion
• Re: Intention to start an [oauth] "working group" Jacob Champion
• Avoid unnecessary processing of DISTINCT clause (Was: Unique Keys) Antonin Houska
• Re: pgsql: doc: remove verbiage about "receiving" data from rep. slots Robert Haas
  • Re: pgsql: doc: remove verbiage about "receiving" data from rep. slots Bruce Momjian
• Use strtoi64() in pgbench, replacing its open-coded implementation Heikki Linnakangas
  • Re: Use strtoi64() in pgbench, replacing its open-coded implementation Yuefei Shi
  • Re: Use strtoi64() in pgbench, replacing its open-coded implementation Neil Chen
  • Re: Use strtoi64() in pgbench, replacing its open-coded implementation Tom Lane
  • Re: Use strtoi64() in pgbench, replacing its open-coded implementation Neil Chen
  • Re: Use strtoi64() in pgbench, replacing its open-coded implementation Chao Li
  • Re: Use strtoi64() in pgbench, replacing its open-coded implementation Heikki Linnakangas
  • Re: Use strtoi64() in pgbench, replacing its open-coded implementation Álvaro Herrera
• PG17 version getting installed by default with every package installation Rambabu V
• Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Kirill Reshke
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Dagfinn Ilmari Mannsåker
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Dagfinn Ilmari Mannsåker
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Melanie Plageman
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Chao Li
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Chao Li
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Chao Li
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Melanie Plageman
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Melanie Plageman
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Andres Freund
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Chao Li
• Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? David Geier
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? David Geier
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? David Geier
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? David Geier
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? Lukas Fittl
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? Robert Haas
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? David Geier
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? Robert Haas
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? Hannu Krosing
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? David Geier
• Re: PRI?64 vs Visual Studio (2022) Thomas Munro
  • Re: PRI?64 vs Visual Studio (2022) Tom Lane
  • Re: PRI?64 vs Visual Studio (2022) Thomas Munro
  • Re: PRI?64 vs Visual Studio (2022) Tom Lane
  • Re: PRI?64 vs Visual Studio (2022) Peter Eisentraut
  • Re: PRI?64 vs Visual Studio (2022) Tom Lane
  • Re: PRI?64 vs Visual Studio (2022) Álvaro Herrera
  • Re: PRI?64 vs Visual Studio (2022) Jacob Champion
  • Re: PRI?64 vs Visual Studio (2022) Thomas Munro
  • Re: PRI?64 vs Visual Studio (2022) Tom Lane
  • Re: PRI?64 vs Visual Studio (2022) Tom Lane
  • Re: PRI?64 vs Visual Studio (2022) Thomas Munro
  • Re: PRI?64 vs Visual Studio (2022) Nazir Bilal Yavuz
  • Re: PRI?64 vs Visual Studio (2022) Tom Lane
  • Re: PRI?64 vs Visual Studio (2022) Thomas Munro
  • Re: PRI?64 vs Visual Studio (2022) Peter Eisentraut
  • Re: PRI?64 vs Visual Studio (2022) Thomas Munro
  • Re: PRI?64 vs Visual Studio (2022) Tom Lane
  • Re: PRI?64 vs Visual Studio (2022) Thomas Munro
  • Re: PRI?64 vs Visual Studio (2022) Peter Eisentraut
• Re: [PATCH] Fixed creation of empty .log files during log rotation Laurenz Albe
  • Re: [PATCH] Fixed creation of empty .log files during log rotation Tom Lane
  • Re: [PATCH] Fixed creation of empty .log files during log rotation Michael Paquier
• Re: RFC: Logging plan of the running query Akshat Jaimini
  • Re: RFC: Logging plan of the running query torikoshia
  • Re: RFC: Logging plan of the running query Robert Haas
  • Re: RFC: Logging plan of the running query torikoshia
  • Re: RFC: Logging plan of the running query Robert Haas
  • Re: RFC: Logging plan of the running query torikoshia
• Post-release followup: pg_add_size_overflow() Jacob Champion
  • Re: Post-release followup: pg_add_size_overflow() Chao Li
  • Re: Post-release followup: pg_add_size_overflow() Jacob Champion
  • Re: Post-release followup: pg_add_size_overflow() Michael Paquier
  • Re: Post-release followup: pg_add_size_overflow() Jacob Champion
  • Re: Post-release followup: pg_add_size_overflow() Jacob Champion
• Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Mircea Cadariu
  • Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Mircea Cadariu
  • Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Fujii Masao
  • Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Mircea Cadariu
  • Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Mircea Cadariu
  • Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Fujii Masao
  • Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Mircea Cadariu
  • Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Fujii Masao
  • Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Mircea Cadariu
  • Re:Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication Yilin Zhang
• Re: Eagerly evict bulkwrite strategy ring Melanie Plageman
  • Re: Eagerly evict bulkwrite strategy ring Chao Li
  • Re: Eagerly evict bulkwrite strategy ring Melanie Plageman
  • Re: Eagerly evict bulkwrite strategy ring Melanie Plageman
• Re: pg_utility ? Dmitry Dolgov
  • Re: pg_utility ? Sami Imseih
  • Re: pg_utility ? Komяpa
  • Re: pg_utility ? Christoph Berg
  • Re: pg_utility ? Andreas Karlsson
  • Re: pg_utility ? Christoph Berg
  • Re: pg_utility ? Andreas Karlsson
  • Re: pg_utility ? Komяpa
  • Re: pg_utility ? Christoph Berg
  • Re: pg_utility ? Komяpa
  • Re: pg_utility ? Aleksander Alekseev
• Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Chao Li
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Chao Li
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Chao Li
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Chao Li
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Kirill Reshke
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Kirill Reshke
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Jelte Fennema-Nio
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Amit Kapila
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Fujii Masao
  • Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect Amit Kapila
• IS JSON predicate support for domain base type as JSON/JSONB/BYTEA/TEXT jian he
  • Re: IS JSON predicate support for domain base type as JSON/JSONB/BYTEA/TEXT Tom Lane
  • Re: IS JSON predicate support for domain base type as JSON/JSONB/BYTEA/TEXT jian he
• Re: Bug in amcheck? Konstantin Knizhnik
  • Re: Bug in amcheck? Mihail Nikalayeu
  • Re: Bug in amcheck? Heikki Linnakangas
  • Re: Bug in amcheck? Peter Geoghegan
  • Re: Bug in amcheck? Heikki Linnakangas
  • Re: Bug in amcheck? Heikki Linnakangas
  • Re: Bug in amcheck? Peter Geoghegan
  • Re: Bug in amcheck? Heikki Linnakangas
• *_LAST in enums to define NUM* macross Roman Khapov
  • Re: *_LAST in enums to define NUM* macross Tom Lane
  • Re: *_LAST in enums to define NUM* macross Roman Khapov
• Re: Ambiguity in IS JSON description and logic Ilmar Y
• Re: Exit walsender before confirming remote flush in logical replication Andrey Silitskiy
  • Re: Exit walsender before confirming remote flush in logical replication Fujii Masao
  • Re: Exit walsender before confirming remote flush in logical replication Andrey Silitskiy
  • Re: Exit walsender before confirming remote flush in logical replication Fujii Masao
  • Re: Exit walsender before confirming remote flush in logical replication Andrey Silitskiy
• Re: Report bytes and transactions actually sent downtream Amit Kapila
  • Re: Report bytes and transactions actually sent downtream Ashutosh Bapat
  • Re: Report bytes and transactions actually sent downtream Amit Kapila
• Fix typos in ExecChooseHashTableSize() Tender Wang
  • Re: Fix typos in ExecChooseHashTableSize() Richard Guo
  • Re: Fix typos in ExecChooseHashTableSize() Tender Wang
• GUC thread-safety approaches Peter Eisentraut
  • Re: GUC thread-safety approaches Heikki Linnakangas
  • Re: GUC thread-safety approaches Peter Eisentraut
  • Re: GUC thread-safety approaches Jelte Fennema-Nio
  • Re: GUC thread-safety approaches Tom Lane
  • Re: GUC thread-safety approaches Peter Eisentraut
  • Re: GUC thread-safety approaches Nico Williams
  • Re: GUC thread-safety approaches David Rowley
  • Re: GUC thread-safety approaches Peter Eisentraut
  • Re: GUC thread-safety approaches Matthias van de Meent
• Why is_admin_of_role() use ROLERECURSE_MEMBERS rather than ROLERECURSE_PRIVS? cca5507
  • Re: Why is_admin_of_role() use ROLERECURSE_MEMBERS rather than ROLERECURSE_PRIVS? cca5507
  • Re: Why is_admin_of_role() use ROLERECURSE_MEMBERS rather than ROLERECURSE_PRIVS? cca5507
• Add a berief general comment on BTScanInsertData's nextkey and backward Yugo Nagata
  • Re: Add a berief general comment on BTScanInsertData's nextkey and backward Peter Geoghegan
• Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID Andrey Borodin
  • Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID Peter Geoghegan
  • Re: nbtree VACUUM's REDO routine doesn't clear page's VACUUM cycle ID Andrey Borodin
• Re: Add os_page_num to pg_buffercache Michael Paquier
  • Re: Add os_page_num to pg_buffercache Bertrand Drouvot
  • Re: Add os_page_num to pg_buffercache Michael Paquier
  • Re: Add os_page_num to pg_buffercache Bertrand Drouvot
  • Re: Add os_page_num to pg_buffercache Bertrand Drouvot
  • Re: Add os_page_num to pg_buffercache Bertrand Drouvot
  • Re: Add os_page_num to pg_buffercache Michael Paquier
• Re: Row pattern recognition Chao Li
  • Re: Row pattern recognition Chao Li
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Vik Fearing
  • Re: Row pattern recognition Chao Li
  • Re: Row pattern recognition Chao Li
  • Re: Row pattern recognition Chao Li
  • Re: Row pattern recognition Chao Li
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Chao Li
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Chao Li
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Tatsuo Ishii
  • Re: Row pattern recognition Tatsuo Ishii

• Earlier messages
• Later messages