pgsql-hackers  

Messages by Thread

• Re: support fast default for domain with constraints jian he
  • Re: support fast default for domain with constraints jian he
• finish TODOs in to_json_is_immutable, to_jsonb_is_immutable also add tests on it jian he
  • Re: finish TODOs in to_json_is_immutable, to_jsonb_is_immutable also add tests on it jian he
• Violation of principle that plan trees are read-only Tom Lane
  • Re: Violation of principle that plan trees are read-only Robert Haas
  • Re: Violation of principle that plan trees are read-only Isaac Morland
  • Re: Violation of principle that plan trees are read-only Tom Lane
  • Re: Violation of principle that plan trees are read-only Jose Luis Tallon
  • Re: Violation of principle that plan trees are read-only Yasir
  • Re: Violation of principle that plan trees are read-only Nico Williams
  • Re: Violation of principle that plan trees are read-only Jose Luis Tallon
  • Re: Violation of principle that plan trees are read-only Tom Lane
  • Re: Violation of principle that plan trees are read-only Robert Haas
  • Re: Violation of principle that plan trees are read-only Andres Freund
  • Re: Violation of principle that plan trees are read-only Andres Freund
  • Re: Violation of principle that plan trees are read-only Tom Lane
  • Re: Violation of principle that plan trees are read-only Tom Lane
  • Re: Violation of principle that plan trees are read-only Andres Freund
  • Re: Violation of principle that plan trees are read-only Tom Lane
  • Re: Violation of principle that plan trees are read-only Andres Freund
  • Re: Violation of principle that plan trees are read-only Tom Lane
  • Re: Violation of principle that plan trees are read-only Tom Lane
  • Re: Violation of principle that plan trees are read-only Tom Lane
• Support for Physical Column Reordering in PG Srinath Reddy Sadipiralla
  • Re: Support for Physical Column Reordering in PG Tom Lane
• Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Álvaro Herrera
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Mihail Nikalayeu
  • Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements Sergey Sargsyan
• Suggestion: Update Copyright Year to 2025 in Recently Added Files Shaik Mohammad Mujeeb
  • Re: Suggestion: Update Copyright Year to 2025 in Recently Added Files Michael Paquier
  • Re: Suggestion: Update Copyright Year to 2025 in Recently Added Files Tom Lane
  • Re: Suggestion: Update Copyright Year to 2025 in Recently Added Files Michael Paquier
  • Re: Suggestion: Update Copyright Year to 2025 in Recently Added Files Bruce Momjian
• Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY Mihail Nikalayeu
• Re: [BUG?] check_exclusion_or_unique_constraint false negative Mihail Nikalayeu
  • Re: [BUG?] check_exclusion_or_unique_constraint false negative Mihail Nikalayeu
  • Re: [BUG?] check_exclusion_or_unique_constraint false negative Mihail Nikalayeu
• To make pg_dump and pg_restore parallel in processing limited number of LOs fkfk000
  • Re: To make pg_dump and pg_restore parallel in processing limited number of LOs Tom Lane
• Find comment on SearchSysCacheLockedCopy1 Paul A Jungwirth
  • Re: Find comment on SearchSysCacheLockedCopy1 Daniel Gustafsson
• Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Aya Iwata (Fujitsu)
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Tomas Vondra
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Timur Magomedov
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Timur Magomedov
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Jim Nasby
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Tomas Vondra
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Jim Nasby
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Jim Nasby
  • Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Peter Smith
• Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Sami Imseih
  • Re: Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Sami Imseih
  • Re: Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Sami Imseih
  • Re: Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Sami Imseih
  • Re: Possible regression in PG18 beta1 Sadeq Dousti
  • Re: Possible regression in PG18 beta1 Maciek Sakrejda
  • Re: Possible regression in PG18 beta1 Peter Geoghegan
• Re: Add Option To Check All Addresses For Matching target_session_attr Andrew Jackson
• pg_upgrade ability to create extension from scripts Regina Obe
  • Re: pg_upgrade ability to create extension from scripts Andreas Karlsson
  • RE: pg_upgrade ability to create extension from scripts Regina Obe
  • Re: pg_upgrade ability to create extension from scripts Andreas Karlsson
• Foreign key isolation tests Paul A Jungwirth
• Proposal: Make cfbot fail on patches not created by "git format-patch" Jelte Fennema-Nio
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Daniel Gustafsson
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Jelte Fennema-Nio
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Aleksander Alekseev
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Jacob Champion
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Florents Tselai
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Tom Lane
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Jacob Champion
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Jelte Fennema-Nio
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Tom Lane
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" Ashutosh Bapat
  • Re: Proposal: Make cfbot fail on patches not created by "git format-patch" David G. Johnston
• Make wal_receiver_timeout configurable per subscription Fujii Masao
  • Re: Make wal_receiver_timeout configurable per subscription Srinath Reddy Sadipiralla
  • Re: Make wal_receiver_timeout configurable per subscription Amit Kapila
  • Re: Make wal_receiver_timeout configurable per subscription Robert Haas
  • Re: Make wal_receiver_timeout configurable per subscription Michael Paquier
  • Re: Make wal_receiver_timeout configurable per subscription vignesh C
  • Re: Make wal_receiver_timeout configurable per subscription Masahiko Sawada
  • Re: Make wal_receiver_timeout configurable per subscription Fujii Masao
  • Re: Make wal_receiver_timeout configurable per subscription Amit Kapila
  • Re: Make wal_receiver_timeout configurable per subscription Fujii Masao
• Document default values for pgoutput options + fix missing initialization for "origin" Fujii Masao
  • Re: Document default values for pgoutput options + fix missing initialization for "origin" Euler Taveira
  • Re: Document default values for pgoutput options + fix missing initialization for "origin" Amit Kapila
  • Re: Document default values for pgoutput options + fix missing initialization for "origin" Fujii Masao
  • Re: Document default values for pgoutput options + fix missing initialization for "origin" Fujii Masao
• PG 17.2 compilation fails with -std=c11 on mac Lakshmi Narayana Velayudam
  • Re: PG 17.2 compilation fails with -std=c11 on mac Tom Lane
  • Re: PG 17.2 compilation fails with -std=c11 on mac Tom Lane
  • Re: PG 17.2 compilation fails with -std=c11 on mac Tom Lane
• C extension compilation failed while using PG 17.2 on mac m1 Lakshmi Narayana Velayudam
  • Re: C extension compilation failed while using PG 17.2 on mac m1 Tom Lane
• wrong query results on bf leafhopper Andres Freund
  • Re: wrong query results on bf leafhopper Alena Rybakina
  • Re: wrong query results on bf leafhopper Robins Tharakan
  • Re: wrong query results on bf leafhopper Andres Freund
  • Re: wrong query results on bf leafhopper David Rowley
  • Re: wrong query results on bf leafhopper Tom Lane
  • Re: wrong query results on bf leafhopper David Rowley
  • Re: wrong query results on bf leafhopper Tomas Vondra
  • Re: wrong query results on bf leafhopper Robins Tharakan
  • Re: wrong query results on bf leafhopper Tom Lane
  • Re: wrong query results on bf leafhopper Andres Freund
  • Re: wrong query results on bf leafhopper Robins Tharakan
• Align wording on copyright organization Daniel Gustafsson
  • Re: Align wording on copyright organization Dave Page
  • Re: Align wording on copyright organization Tom Lane
  • Re: Align wording on copyright organization Daniel Gustafsson
  • Re: Align wording on copyright organization Daniel Gustafsson
  • Re: Align wording on copyright organization Dave Page
• Re: Virtual generated columns Alexander Lakhin
  • Re: Virtual generated columns Richard Guo
  • Re: Virtual generated columns jian he
  • Re: Virtual generated columns Richard Guo
  • Re: Virtual generated columns jian he
• Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding Peter Smith
  • Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding Amit Kapila
  • Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding Ajin Cherian
  • Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding Ajin Cherian
  • Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding Ajin Cherian
• Binary operators for cubes Kirill Panin
• Add comment explaining why queryid is int64 in pg_stat_statements Shaik Mohammad Mujeeb
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Ilia Evdokimov
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Shaik Mohammad Mujeeb
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements wenhui qiu
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Shaik Mohammad Mujeeb
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Junwang Zhao
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Peter Eisentraut
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Sami Imseih
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Lukas Fittl
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Sami Imseih
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Peter Eisentraut
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Nathan Bossart
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Shaik Mohammad Mujeeb
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Julien Rouhaud
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements David Rowley
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Michael Paquier
  • Re: Add comment explaining why queryid is int64 in pg_stat_statements Julien Rouhaud
• Re: Update LDAP Protocol in fe-connect.c to v3 Pavel Seleznev
  • Re: Update LDAP Protocol in fe-connect.c to v3 Peter Eisentraut
• Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • RE: Conflict detection for update_deleted in logical replication Zhijie Hou (Fujitsu)
  • RE: Conflict detection for update_deleted in logical replication Zhijie Hou (Fujitsu)
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • RE: Conflict detection for update_deleted in logical replication Zhijie Hou (Fujitsu)
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication shveta malik
  • Re: Conflict detection for update_deleted in logical replication Amit Kapila

• Earlier messages
• Later messages