pgsql-hackers  

Messages by Thread

• Improve planner cost estimations for alternative subplans Alexey Bashtanov
• minor doc fix - garbage in example of result of unnest Pavel Stehule
  • Re: minor doc fix - garbage in example of result of unnest Tom Lane
  • Re: minor doc fix - garbage in example of result of unnest Tomas Vondra
  • Re: minor doc fix - garbage in example of result of unnest David G. Johnston
  • Re: minor doc fix - garbage in example of result of unnest Tom Lane
• Make more use of RELKIND_HAS_STORAGE() Peter Eisentraut
  • Re: Make more use of RELKIND_HAS_STORAGE() Tom Lane
• REL_13_STABLE Branch Jonathan S. Katz
• [PATCH] pg_dump: Add example and link for --encoding option 이동욱
  • Re: [PATCH] pg_dump: Add example and link for --encoding option 이동욱
• Regarding TZ conversion Rajin Raj
  • Re: Regarding TZ conversion Tom Lane
  • Re: Regarding TZ conversion Rajin Raj
• Possible bug on Postgres 12 (CASE THEN evaluated prematurely) - Change of behaviour compared to 11, 10, 9 Juan Fuentes
  • Re: Possible bug on Postgres 12 (CASE THEN evaluated prematurely) - Change of behaviour compared to 11, 10, 9 Tom Lane
  • Re: Possible bug on Postgres 12 (CASE THEN evaluated prematurely) - Change of behaviour compared to 11, 10, 9 Juan Fuentes
• [PATCH] Leading minus for negative time interval in ISO 8601 Mikhail Titov
  • Re: [PATCH] Leading minus for negative time interval in ISO 8601 Tom Lane
  • Re: [PATCH] Leading minus for negative time interval in ISO 8601 Chapman Flack
  • Re: [PATCH] Leading minus for negative time interval in ISO 8601 Tom Lane
  • Re: [PATCH] Leading minus for negative time interval in ISO 8601 Mikhail Titov
  • Re: [PATCH] Leading minus for negative time interval in ISO 8601 Mikhail Titov
• question regarding copyData containers Jerome Wagner
  • Re: question regarding copyData containers Tom Lane
  • Re: question regarding copyData containers Andres Freund
  • Re: question regarding copyData containers Jerome Wagner
• libpq copy error handling busted Andres Freund
  • Re: libpq copy error handling busted Tom Lane
  • Re: libpq copy error handling busted Tom Lane
  • Re: libpq copy error handling busted Thomas Munro
  • Re: libpq copy error handling busted Thomas Munro
  • Re: libpq copy error handling busted Thomas Munro
  • Re: libpq copy error handling busted Oleksandr Shulgin
  • Re: libpq copy error handling busted Thomas Munro
  • Re: libpq copy error handling busted Tom Lane
• Atomic operations within spinlocks Tom Lane
  • Re: Atomic operations within spinlocks Andres Freund
  • Re: Atomic operations within spinlocks Thomas Munro
  • Re: Atomic operations within spinlocks Michael Paquier
  • Re: Atomic operations within spinlocks Tom Lane
  • Re: Atomic operations within spinlocks Tom Lane
  • Re: Atomic operations within spinlocks Andres Freund
  • Re: Atomic operations within spinlocks Tom Lane
  • Re: Atomic operations within spinlocks Andres Freund
  • Re: Atomic operations within spinlocks Andres Freund
  • Re: Atomic operations within spinlocks Tom Lane
  • Re: Atomic operations within spinlocks Andres Freund
• Towards easier AMs: Cleaning up inappropriate use of name "relkind" Mark Dilger
  • Re: Towards easier AMs: Cleaning up inappropriate use of name "relkind" Alvaro Herrera
• significant slowdown of HashAggregate between 9.6 and 10 Pavel Stehule
  • Re: significant slowdown of HashAggregate between 9.6 and 10 Pavel Stehule
  • Re: significant slowdown of HashAggregate between 9.6 and 10 Tomas Vondra
  • Re: significant slowdown of HashAggregate between 9.6 and 10 Andres Freund
  • Re: significant slowdown of HashAggregate between 9.6 and 10 Andres Freund
  • Re: significant slowdown of HashAggregate between 9.6 and 10 Jeff Davis
  • Re: significant slowdown of HashAggregate between 9.6 and 10 Andres Freund
  • Re: significant slowdown of HashAggregate between 9.6 and 10 Tomas Vondra
  • Re: significant slowdown of HashAggregate between 9.6 and 10 Andres Freund
• how to create index concurrently on paritioned table 李杰(慎追)
• Re: Asynchronous Append on postgres_fdw nodes. Andrey Lepikhov
  • Re: Asynchronous Append on postgres_fdw nodes. Kyotaro Horiguchi
• REINDEX CONCURRENTLY and indisreplident Michael Paquier
  • Re: REINDEX CONCURRENTLY and indisreplident Euler Taveira
  • Re: REINDEX CONCURRENTLY and indisreplident Michael Paquier
  • Re: REINDEX CONCURRENTLY and indisreplident Michael Paquier
• Removal of currtid()/currtid2() and some table AM cleanup Michael Paquier
  • Re: Removal of currtid()/currtid2() and some table AM cleanup Tom Lane
  • Re: Removal of currtid()/currtid2() and some table AM cleanup Tom Lane
  • Re: Removal of currtid()/currtid2() and some table AM cleanup Inoue, Hiroshi
  • Re: Removal of currtid()/currtid2() and some table AM cleanup Michael Paquier
  • Re: Removal of currtid()/currtid2() and some table AM cleanup Inoue, Hiroshi
  • Re: Removal of currtid()/currtid2() and some table AM cleanup Andres Freund
  • Re: Removal of currtid()/currtid2() and some table AM cleanup Michael Paquier
• Re: Command statistics system (cmdstats) Mark Dilger
  • Re: Command statistics system (cmdstats) Mark Dilger
• elog(DEBUG2 in SpinLocked section. Kyotaro Horiguchi
  • Re: elog(DEBUG2 in SpinLocked section. Fujii Masao
  • Re: elog(DEBUG2 in SpinLocked section. Amit Kapila
  • Re: elog(DEBUG2 in SpinLocked section. Fujii Masao
  • Re: elog(DEBUG2 in SpinLocked section. Kyotaro Horiguchi
  • Re: elog(DEBUG2 in SpinLocked section. Michael Paquier
  • Re: elog(DEBUG2 in SpinLocked section. Amit Kapila
  • Re: elog(DEBUG2 in SpinLocked section. Michael Paquier
  • Re: elog(DEBUG2 in SpinLocked section. Tom Lane
  • Re: elog(DEBUG2 in SpinLocked section. Michael Paquier
  • Re: elog(DEBUG2 in SpinLocked section. Tom Lane
  • Re: elog(DEBUG2 in SpinLocked section. Michael Paquier
  • Re: elog(DEBUG2 in SpinLocked section. Tom Lane
  • Re: elog(DEBUG2 in SpinLocked section. Tom Lane
  • Re: elog(DEBUG2 in SpinLocked section. Kyotaro Horiguchi
  • Re: elog(DEBUG2 in SpinLocked section. Tom Lane
  • Re: elog(DEBUG2 in SpinLocked section. Michael Paquier
  • Re: elog(DEBUG2 in SpinLocked section. Tom Lane
• Resetting spilled txn statistics in pg_stat_replication Masahiko Sawada
  • Re: Resetting spilled txn statistics in pg_stat_replication Kyotaro Horiguchi
  • Re: Resetting spilled txn statistics in pg_stat_replication Fujii Masao
  • Re: Resetting spilled txn statistics in pg_stat_replication Masahiko Sawada
  • Re: Resetting spilled txn statistics in pg_stat_replication Amit Kapila
  • Re: Resetting spilled txn statistics in pg_stat_replication Masahiko Sawada
  • Re: Resetting spilled txn statistics in pg_stat_replication Amit Kapila
• Small doc improvement about spilled txn tracking Masahiko Sawada
  • Re: Small doc improvement about spilled txn tracking Amit Kapila
  • Re: Small doc improvement about spilled txn tracking Amit Kapila
  • Re: Small doc improvement about spilled txn tracking Masahiko Sawada
  • Re: Small doc improvement about spilled txn tracking Amit Kapila
  • Re: Small doc improvement about spilled txn tracking Masahiko Sawada
• Small code cleanup Mark Dilger
  • Re: Small code cleanup Tom Lane
  • Re: Small code cleanup Mark Dilger
  • Re: Small code cleanup Tom Lane
  • Re: Small code cleanup Mark Dilger
• Wrong width of UNION statement Kenichiro Tanaka
  • Re: Wrong width of UNION statement Tom Lane
  • Re: Wrong width of UNION statement Kenichiro Tanaka
• [POC] Fast COPY FROM command for the table with foreign partitions Andrey Lepikhov
  • Re: [POC] Fast COPY FROM command for the table with foreign partitions Etsuro Fujita
  • Re: [POC] Fast COPY FROM command for the table with foreign partitions Andrey Lepikhov
• Compatible defaults for LEAD/LAG Vik Fearing
  • Re: Compatible defaults for LEAD/LAG Tom Lane
  • Re: Compatible defaults for LEAD/LAG Vik Fearing
  • Re: Compatible defaults for LEAD/LAG Vik Fearing
  • Re: Compatible defaults for LEAD/LAG Tom Lane
  • Re: Compatible defaults for LEAD/LAG Pavel Stehule
  • Re: Compatible defaults for LEAD/LAG Tom Lane
  • Re: Compatible defaults for LEAD/LAG Pavel Stehule
• A wrong index choose issue because of inaccurate statistics Andy Fan
  • Re: A wrong index choose issue because of inaccurate statistics Andy Fan
  • Re: A wrong index choose issue because of inaccurate statistics David Rowley
  • Re: A wrong index choose issue because of inaccurate statistics Pavel Stehule
• Proposal: remove string "contains errors; unaffected changes were applied" Антон Пацев
  • Re: Proposal: remove string "contains errors; unaffected changes were applied" Justin Pryzby
  • Re: Proposal: remove string "contains errors; unaffected changes were applied" Антон Пацев
• Re: pie-in-sky idea: 'sensitive' function parameters Chapman Flack
  • Re: pie-in-sky idea: 'sensitive' function parameters Robert Haas
  • Re: pie-in-sky idea: 'sensitive' function parameters Chapman Flack
  • Re: pie-in-sky idea: 'sensitive' function parameters Tom Lane
  • Re: pie-in-sky idea: 'sensitive' function parameters Robert Haas
  • Re: pie-in-sky idea: 'sensitive' function parameters Tom Lane
  • Re: pie-in-sky idea: 'sensitive' function parameters Chapman Flack
  • Re: pie-in-sky idea: 'sensitive' function parameters Robert Haas
• PG function with pseudotype "anyelement" for IN, OUT parameter shows wrong behaviour. Prabhat Sahu
  • Re: PG function with pseudotype "anyelement" for IN, OUT parameter shows wrong behaviour. Pavel Stehule
  • Re: PG function with pseudotype "anyelement" for IN, OUT parameter shows wrong behaviour. Prabhat Sahu
• proposal: possibility to read dumped table's name from file Pavel Stehule
  • Re: proposal: possibility to read dumped table's name from file Tom Lane
  • Re: proposal: possibility to read dumped table's name from file Pavel Stehule
  • Re: proposal: possibility to read dumped table's name from file David Fetter
  • Re: proposal: possibility to read dumped table's name from file Tom Lane
  • Re: proposal: possibility to read dumped table's name from file Pavel Stehule
  • Re: proposal: possibility to read dumped table's name from file Justin Pryzby
• Re: Speeding up parts of the planner using a binary search tree structure for nodes Ashutosh Bapat
  • Re: Speeding up parts of the planner using a binary search tree structure for nodes David Rowley
  • Re: Speeding up parts of the planner using a binary search tree structure for nodes Amit Langote
• pg_dump fail to not dump public schema orders Adrien Nayrat
  • Re: pg_dump fail to not dump public schema orders David G. Johnston
  • Re: pg_dump fail to not dump public schema orders Tom Lane
  • Re: pg_dump fail to not dump public schema orders Adrien Nayrat
  • Re: pg_dump fail to not dump public schema orders David G. Johnston
• Does PG server process keep backend info brajmohan saxena
• RE: archive status ".ready" files may be created too early matsumura....@fujitsu.com
  • Re: archive status ".ready" files may be created too early Bossart, Nathan
• feature idea: use index when checking for NULLs before SET NOT NULL John Bachir
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL Sergei Kornilov
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL Oleksandr Shulgin
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL Komяpa
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL John Bachir
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL Sergei Kornilov
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL John Bachir
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL Justin Pryzby
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL John Bachir
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL Justin Pryzby
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL John Bachir
  • Re: feature idea: use index when checking for NULLs before SET NOT NULL John Bachir
• OpenSSL 3.0.0 compatibility Daniel Gustafsson
  • Re: OpenSSL 3.0.0 compatibility Laurenz Albe
  • Re: OpenSSL 3.0.0 compatibility Daniel Gustafsson
  • Re: OpenSSL 3.0.0 compatibility Peter Eisentraut
  • Re: OpenSSL 3.0.0 compatibility Daniel Gustafsson
  • Re: OpenSSL 3.0.0 compatibility Peter Eisentraut
  • Re: OpenSSL 3.0.0 compatibility Michael Paquier
  • Re: OpenSSL 3.0.0 compatibility Peter Eisentraut
  • Re: OpenSSL 3.0.0 compatibility Michael Paquier
  • Re: OpenSSL 3.0.0 compatibility Daniel Gustafsson
  • Re: OpenSSL 3.0.0 compatibility Peter Eisentraut
  • Re: OpenSSL 3.0.0 compatibility Andrew Dunstan
  • Re: OpenSSL 3.0.0 compatibility Peter Eisentraut
  • Re: OpenSSL 3.0.0 compatibility Andrew Dunstan
  • Re: OpenSSL 3.0.0 compatibility Daniel Gustafsson
  • Re: OpenSSL 3.0.0 compatibility Andrew Dunstan
  • Re: OpenSSL 3.0.0 compatibility Tom Lane
  • Re: OpenSSL 3.0.0 compatibility Peter Eisentraut
  • Re: OpenSSL 3.0.0 compatibility Andrew Dunstan
  • Re: OpenSSL 3.0.0 compatibility Michael Paquier
• Conflict of implicit collations doesn't propagate out of subqueries Markus Winand
  • Re: Conflict of implicit collations doesn't propagate out of subqueries Tom Lane
  • Re: Conflict of implicit collations doesn't propagate out of subqueries Markus Winand
• Re: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare() Mark Dilger
• Incorrect comment in be-secure-openssl.c Daniel Gustafsson
  • Re: Incorrect comment in be-secure-openssl.c Michael Paquier

• Earlier messages