pgsql-hackers  

Messages by Thread

• Re: WIP: BRIN multi-range indexes Tomas Vondra
• [GSoC] working status Charles Cui
• [GSoC] array processing questions Charles Cui
  • Re: [GSoC] array processing questions Andrew Gierth
  • Re: [GSoC] array processing questions Charles Cui
• pg11b1 from outside a txn: "VACUUM cannot run inside a transaction block": should be: ...or multi-command string Justin Pryzby
  • Re: pg11b1 from outside a txn: "VACUUM cannot run inside a transaction block": should be: ...or multi-command string Andrew Gierth
• Retrieve memory size allocated by libpq Lars Kanis
• Log query parameters for terminated execute Sergei Kornilov
  • Re: Log query parameters for terminated execute Pavel Stehule
• comma to delimit fractional seconds Chris Howard
  • Re: comma to delimit fractional seconds Tom Lane
• postgresql_fdw doesn't handle defaults correctly Pavel Stehule
• effect of JIT tuple deform? Pavel Stehule
  • Re: effect of JIT tuple deform? Pavel Stehule
• Re: Using JSONB directly from application Christian Ohler
  • Re: Using JSONB directly from application Nico Williams
• Psql patch to show access methods info Sergey Cherkashin
• utilities to rebuild commit logs from wal Chris Travers
  • Re: utilities to rebuild commit logs from wal Bruce Momjian
• Lifetime of commit timestamps Kyotaro HORIGUCHI
• Speeding up INSERTs and UPDATEs to partitioned tables David Rowley
  • Re: Speeding up INSERTs and UPDATEs to partitioned tables David Rowley
• Incorrect errno used with %m for backend code Michael Paquier
  • Re: Incorrect errno used with %m for backend code Ashutosh Sharma
  • Re: Incorrect errno used with %m for backend code Michael Paquier
  • Re: Incorrect errno used with %m for backend code Ashutosh Sharma
  • Re: Incorrect errno used with %m for backend code Michael Paquier
  • Re: Incorrect errno used with %m for backend code Ashutosh Sharma
  • Re: Incorrect errno used with %m for backend code Alvaro Herrera
  • Re: Incorrect errno used with %m for backend code Andres Freund
  • Re: Incorrect errno used with %m for backend code Michael Paquier
• Incorrect comments in commit_ts.c shao bret
  • Re: Incorrect comments in commit_ts.c Michael Paquier
  • 答复: Incorrect comments in commit_ts.c shao bret
• PSA: --enable-coverage interferes with parallel query scheduling Tom Lane
  • Re: PSA: --enable-coverage interferes with parallel query scheduling Robert Haas
• Continue work on changes to recovery.conf API Sergei Kornilov
  • Re: Continue work on changes to recovery.conf API Craig Ringer
• Wrong cost estimation for foreign tables join with use_remote_estimate disabled Konstantin Knizhnik
  • Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Tom Lane
  • Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Konstantin Knizhnik
  • Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Etsuro Fujita
  • Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Amit Langote
  • Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Etsuro Fujita
  • Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Ashutosh Bapat
  • Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Ashutosh Bapat
  • Re: Wrong cost estimation for foreign tables join with use_remote_estimate disabled Konstantin Knizhnik
• phraseto_tsquery design Sagiv Some
  • Re: phraseto_tsquery design Arthur Zakirov
• partition table and stddev() /variance() behaviour Rajkumar Raghuwanshi
  • Re: partition table and stddev() /variance() behaviour David Rowley
  • Re: partition table and stddev() /variance() behaviour Tom Lane
  • Re: partition table and stddev() /variance() behaviour David Rowley
  • Re: partition table and stddev() /variance() behaviour David Rowley
  • Re: partition table and stddev() /variance() behaviour Tom Lane
  • Re: partition table and stddev() /variance() behaviour David Rowley
  • Re: partition table and stddev() /variance() behaviour Rajkumar Raghuwanshi
• Re: Sample values for pg_stat_statements Daniel Gustafsson
  • Re: Sample values for pg_stat_statements Michael Paquier
• Making "COPY partitioned_table FROM" faster David Rowley
• "wal receiver" process hang in syslog() while exiting after receiving SIGTERM while the postgres has been promoted. Chen, Yan-Jack (NSB - CN/Hangzhou)
  • Re: "wal receiver" process hang in syslog() while exiting after receiving SIGTERM while the postgres has been promoted. Robert Haas
• Buildfarm failure in rolenames.sql Michael Paquier
• bug with expression index on partition Amit Langote
  • Re: bug with expression index on partition Amit Langote
  • Re: bug with expression index on partition Amit Langote
  • Re: bug with expression index on partition Alvaro Herrera
  • Re: bug with expression index on partition Alvaro Herrera
• changing xpath() and xpath_exists() Alvaro Herrera
  • Re: changing xpath() and xpath_exists() Andrew Dunstan
• Postgres 10.4 crashing when using PLV8 Mukesh Chhatani
  • Re: Postgres 10.4 crashing when using PLV8 David G. Johnston
  • Re: Postgres 10.4 crashing when using PLV8 Mukesh Chhatani
• Re: Push down Aggregates below joins Tomas Vondra
  • Re: Push down Aggregates below joins Tomas Vondra
  • Re: Push down Aggregates below joins Antonin Houska
  • Re: Push down Aggregates below joins Heikki Linnakangas
  • Re: Push down Aggregates below joins Antonin Houska
• memory leak when serializing TRUNCATE in reorderbuffer Tomas Vondra
• [PATCH] Include application_name in "connection authorized" log message Don Seiler
  • Re: [PATCH] Include application_name in "connection authorized" log message Stephen Frost
  • Re: [PATCH] Include application_name in "connection authorized" log message Don Seiler
  • Re: [PATCH] Include application_name in "connection authorized" log message Robert Haas
  • Re: [PATCH] Include application_name in "connection authorized" log message Stephen Frost
  • Re: [PATCH] Include application_name in "connection authorized" log message Robert Haas
  • Re: [PATCH] Include application_name in "connection authorized" log message Stephen Frost
  • Re: [PATCH] Include application_name in "connection authorized" log message Andres Freund
  • Re: [PATCH] Include application_name in "connection authorized" log message Alvaro Herrera
  • Re: [PATCH] Include application_name in "connection authorized" log message Andres Freund
  • Re: [PATCH] Include application_name in "connection authorized" log message Alvaro Herrera
  • Re: [PATCH] Include application_name in "connection authorized" log message Andres Freund
  • Re: [PATCH] Include application_name in "connection authorized" log message Alvaro Herrera
• Re: Allow auto_explain to log to NOTICE Daniel Gustafsson
• Re: [HACKERS] WIP: long transactions on hot standby feedback replica / proof of concept Alexander Korotkov
• line numbers in error messages are off wrt debuggers Andres Freund
  • Re: line numbers in error messages are off wrt debuggers Tom Lane
  • Re: line numbers in error messages are off wrt debuggers Andres Freund
  • Re: line numbers in error messages are off wrt debuggers Tom Lane
  • Re: line numbers in error messages are off wrt debuggers Andres Freund
  • Re: line numbers in error messages are off wrt debuggers Tom Lane
• PATCH: backtraces for error messages Craig Ringer
  • Re: PATCH: backtraces for error messages Alvaro Herrera
  • Re: PATCH: backtraces for error messages Andres Freund
  • Re: PATCH: backtraces for error messages Tom Lane
  • Re: PATCH: backtraces for error messages Andres Freund
  • Re: PATCH: backtraces for error messages Robert Haas
  • Re: PATCH: backtraces for error messages Andres Freund
  • Re: PATCH: backtraces for error messages Robert Haas
  • Re: PATCH: backtraces for error messages Craig Ringer
  • Re: PATCH: backtraces for error messages Craig Ringer
  • Re: PATCH: backtraces for error messages Michael Paquier
  • Re: PATCH: backtraces for error messages Pavan Deolasee
  • Re: PATCH: backtraces for error messages Craig Ringer
  • Re: PATCH: backtraces for error messages Andres Freund
  • Re: PATCH: backtraces for error messages Pavan Deolasee
  • Re: PATCH: backtraces for error messages Craig Ringer
  • Re: PATCH: backtraces for error messages Korry Douglas
  • Re: PATCH: backtraces for error messages Craig Ringer
  • Re: PATCH: backtraces for error messages Craig Ringer
  • Re: PATCH: backtraces for error messages Kyotaro HORIGUCHI
  • RE: PATCH: backtraces for error messages Tsunakawa, Takayuki
  • Re: PATCH: backtraces for error messages Alexander Kuzmenkov
  • Re: PATCH: backtraces for error messages Daniel Gustafsson
• ERROR: ORDER/GROUP BY expression not found in targetlist Rajkumar Raghuwanshi
  • Re: ERROR: ORDER/GROUP BY expression not found in targetlist Tom Lane
  • Re: ERROR: ORDER/GROUP BY expression not found in targetlist Tom Lane
  • Re: ERROR: ORDER/GROUP BY expression not found in targetlist Rajkumar Raghuwanshi
• Re: documentation is now XML Liudmila Mantrova
  • Re: documentation is now XML Bruce Momjian
  • Re: documentation is now XML Alexander Lakhin
  • Re: documentation is now XML Bruce Momjian
  • Re: documentation is now XML Tatsuo Ishii
• New function pg_stat_statements_reset_query() to reset statistics of a specific query Haribabu Kommi
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Daniel Gustafsson
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Jeremy Schneider
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Sergei Kornilov
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Euler Taveira
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Robert Haas
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Rui DeSousa
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Euler Taveira
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Haribabu Kommi
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Ashutosh Sharma
  • Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query Ashutosh Sharma
• Re: Parallel Aggregates for string_agg and array_agg David Rowley
• pglife and post-beta commits Bruce Momjian
• Re: XML/XPath issues: text/CDATA in XMLTABLE, XPath evaluated with wrong context Alvaro Herrera
  • Re: XML/XPath issues: text/CDATA in XMLTABLE, XPath evaluated with wrong context Alvaro Herrera
  • Re: XML/XPath issues: text/CDATA in XMLTABLE, XPath evaluated with wrong context Alvaro Herrera
• Re: [HACKERS] Custom compression methods Robert Haas
• Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andres Freund
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Andrew Dunstan
  • Re: Fast default stuff versus pg_upgrade Alvaro Herrera
  • Re: Fast default stuff versus pg_upgrade Tom Lane
  • Re: Fast default stuff versus pg_upgrade Robert Haas
  • Re: Fast default stuff versus pg_upgrade Peter Geoghegan
  • Re: Fast default stuff versus pg_upgrade David G. Johnston
  • Re: Fast default stuff versus pg_upgrade Tom Lane
• Re: MERGE SQL statement for PG12 Andrew Dunstan
  • Re: MERGE SQL statement for PG12 Pavan Deolasee
  • Re: MERGE SQL statement for PG12 Peter Geoghegan
• Possible Spinlock impact of highly increased latency of PAUSE instruction on Skylake Hans Buschmann
• pg_verify_checksums review Daniel Gustafsson
  • Re: pg_verify_checksums review Magnus Hagander
• documenting forbidden expressions in column defaults Amit Langote

• Earlier messages