pgsql-hackers  

Messages by Thread

• • Re: IPC/MultixactCreation on the Standby server Andrey Borodin
  • Re: IPC/MultixactCreation on the Standby server Dmitry
  • page_collect_tuples without long lock on page (Was Re: IPC/MultixactCreation on the Standby server) Yura Sokolov
• Re: Covering the comparison between date and timestamp, tz, type Tom Lane
• PostgreSQL 16 bug feedback yexiu-glory
  • Re: PostgreSQL 16 bug feedback David G. Johnston
  • Re: PostgreSQL 16 bug feedback yexiu-glory
  • Re: PostgreSQL 16 bug feedback David G. Johnston
  • Re: PostgreSQL 16 bug feedback Laurenz Albe
  • Re: PostgreSQL 16 bug feedback yexiu-glory
• Re: generic plans and "initial" pruning Amit Langote
  • Re: generic plans and "initial" pruning Amit Langote
• [Feature Request] Support INSERT ... FROM ... TO for date ranges zkbp712
  • Re: [Feature Request] Support INSERT ... FROM ... TO for date ranges Álvaro Herrera
• Re: psql: tab-completion support for COPY ... TO/FROM STDIN, STDOUT, and PROGRAM Yugo Nagata
  • Re: psql: tab-completion support for COPY ... TO/FROM STDIN, STDOUT, and PROGRAM Yugo Nagata
• Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? Andres Freund
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? Lukas Fittl
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? Michael Paquier
  • Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? Michael Paquier
• simple patch for discussion Greg Hennessy
  • Re: simple patch for discussion David Rowley
  • Re: simple patch for discussion Greg Hennessy
  • Re: simple patch for discussion Maciek Sakrejda
  • Re: simple patch for discussion Andy Fan
  • Re: simple patch for discussion Andres Freund
  • Re: simple patch for discussion David Rowley
  • simple patch for discussion David G. Johnston
  • Re: simple patch for discussion David Rowley
  • Re: simple patch for discussion David G. Johnston
  • Re: simple patch for discussion David G. Johnston
  • Re: simple patch for discussion Greg Hennessy
  • Re: simple patch for discussion David Rowley
  • Re: simple patch for discussion Greg Hennessy
  • Re: simple patch for discussion David Rowley
• duplicate line in ExecEvalJsonCoercionFinish jian he
  • Re: duplicate line in ExecEvalJsonCoercionFinish Tender Wang
  • Re: duplicate line in ExecEvalJsonCoercionFinish Richard Guo
  • Re: duplicate line in ExecEvalJsonCoercionFinish Amit Langote
  • Re: duplicate line in ExecEvalJsonCoercionFinish Amit Langote
• Re: Returning nbtree posting list TIDs in DESC order during backwards scans Mircea Cadariu
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Peter Geoghegan
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Peter Geoghegan
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Mircea Cadariu
  • Re: Returning nbtree posting list TIDs in DESC order during backwards scans Andy Fan
• Re: [PATCH] avoid double scanning in function byteain Tom Lane
  • Re: [PATCH] avoid double scanning in function byteain Tom Lane
  • Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • Re: [PATCH] avoid double scanning in function byteain David G. Johnston
  • Re: [PATCH] avoid double scanning in function byteain Stepan Neretin
  • [PATCH] avoid double scanning in function byteain David G. Johnston
  • Re: [PATCH] avoid double scanning in function byteain Tom Lane
• Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available Tom Lane
  • Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available Tom Lane
  • Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available Andres Freund
• Re: [PATCH] Add tests for binaryheap.c Nathan Bossart
  • Re: [PATCH] Add tests for binaryheap.c Aleksander Alekseev
  • Re: [PATCH] Add tests for binaryheap.c Nathan Bossart
• Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET Dagfinn Ilmari Mannsåker
  • Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET jian he
  • Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET Dagfinn Ilmari Mannsåker
  • Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET Tomas Vondra
  • Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET Dagfinn Ilmari Mannsåker
  • Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET Tomas Vondra
  • Re: Fix tab completion in v18 for ALTER DATABASE/USER/ROLE ... RESET Dagfinn Ilmari Mannsåker
• Re: pg_dumpall dumps global objects with --statistics-only or --no-schema Jeff Davis
• Re: Fix PQport to never return NULL if the connection is valid Laurenz Albe
  • Re: Fix PQport to never return NULL if the connection is valid Tom Lane
  • Re: Fix PQport to never return NULL if the connection is valid Laurenz Albe
  • Re: Fix PQport to never return NULL if the connection is valid Tom Lane
  • Re: Fix PQport to never return NULL if the connection is valid Laurenz Albe
• Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Andres Freund
  • Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Yura Sokolov
  • Re: Read-Write optimistic lock (Re: sinvaladt.c: remove msgnumLock, use atomic operations on maxMsgNum) Andres Freund
• wrong sequence value in dump file Fabrice Chapuis
  • Re: wrong sequence value in dump file Tom Lane
  • Re: wrong sequence value in dump file Fabrice Chapuis
• Composite types for updatable views Malthe
  • Re: Composite types for updatable views DINESH NAIR
• event trigger support for PL/Python Euler Taveira
  • Re: event trigger support for PL/Python Pavel Stehule
  • Re: event trigger support for PL/Python Euler Taveira
  • Re: event trigger support for PL/Python Pavel Stehule
  • Re: event trigger support for PL/Python Pavel Stehule
  • Re: event trigger support for PL/Python Euler Taveira
  • Re: event trigger support for PL/Python Pavel Stehule
  • Re: event trigger support for PL/Python Euler Taveira
  • Re: event trigger support for PL/Python Pavel Stehule
• Fix lwlock.c and wait_event_names.txt discrepancy Bertrand Drouvot
  • Re: Fix lwlock.c and wait_event_names.txt discrepancy Michael Paquier
  • Re: Fix lwlock.c and wait_event_names.txt discrepancy Álvaro Herrera
  • Re: Fix lwlock.c and wait_event_names.txt discrepancy Bertrand Drouvot
  • Re: Fix lwlock.c and wait_event_names.txt discrepancy Michael Paquier
  • Re: Fix lwlock.c and wait_event_names.txt discrepancy Bertrand Drouvot
  • Re: Fix lwlock.c and wait_event_names.txt discrepancy Bertrand Drouvot
• 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 Sami Imseih
  • 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 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 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
• Resetting recovery target parameters in pg_createsubscriber D Laaren
• Re: ZStandard (with dictionaries) compression support for TOAST compression Michael Paquier
  • Re: ZStandard (with dictionaries) compression support for TOAST compression Nikhil Kumar Veldanda
  • Re: ZStandard (with dictionaries) compression support for TOAST compression Michael Paquier
• Re: Document default values for pgoutput options + fix missing initialization for "origin" Fujii Masao
• Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Tom Lane
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Andres Freund
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Alexander Lakhin
  • Re: Improve error reporting in 027_stream_regress test Tom Lane
  • Re: Improve error reporting in 027_stream_regress test Michael Paquier
  • Re: Improve error reporting in 027_stream_regress test Nazir Bilal Yavuz
  • Re: Improve error reporting in 027_stream_regress test Tom Lane
• Collation and primary keys Jeff Davis
  • Re: Collation and primary keys Laurenz Albe
  • Re: Collation and primary keys Jeff Davis
  • Re: Collation and primary keys Laurenz Albe
  • Re: Collation and primary keys Jeff Davis
  • Re: Collation and primary keys Laurenz Albe
  • Re: Collation and primary keys Daniel Verite
  • Re: Collation and primary keys Jeff Davis
• IndexAmRoutine aminsertcleanup function can be NULL? Peter Smith
  • Re: IndexAmRoutine aminsertcleanup function can be NULL? Japin Li
  • Re: IndexAmRoutine aminsertcleanup function can be NULL? Michael Paquier
  • Re: IndexAmRoutine aminsertcleanup function can be NULL? Peter Smith
  • Re: IndexAmRoutine aminsertcleanup function can be NULL? Japin Li
  • Re: IndexAmRoutine aminsertcleanup function can be NULL? Michael Paquier
  • Re: IndexAmRoutine aminsertcleanup function can be NULL? Michael Paquier
• Eagerly evict bulkwrite strategy ring Melanie Plageman
• Re: postgres_fdw could deparse ArrayCoerceExpr Alexander Korotkov
  • Re: postgres_fdw could deparse ArrayCoerceExpr Tender Wang
  • Re: postgres_fdw could deparse ArrayCoerceExpr Alexander Korotkov
• Re: Removing unneeded self joins Alexander Korotkov
  • Re: Removing unneeded self joins Michael Paquier
  • Re: Removing unneeded self joins Alexander Korotkov
• Re: Tags in the commitfest app: How to use them and what tags to add? Jelte Fennema-Nio
  • Re: Tags in the commitfest app: How to use them and what tags to add? Jacob Champion
  • Re: Tags in the commitfest app: How to use them and what tags to add? Jacob Champion
  • Re: Tags in the commitfest app: How to use them and what tags to add? Jacob Champion
  • Re: Tags in the commitfest app: How to use them and what tags to add? Jelte Fennema-Nio
• refactor backend type lists Álvaro Herrera
  • Re: refactor backend type lists Euler Taveira

• Earlier messages
• Later messages