pgsql-hackers  

Messages by Thread

• • Re: pg_publication_tables: return NULL attnames when no column list is specified Roberto Mello
  • Re: pg_publication_tables: return NULL attnames when no column list is specified Ajin Cherian
  • Re: pg_publication_tables: return NULL attnames when no column list is specified Amit Kapila
  • Re: pg_publication_tables: return NULL attnames when no column list is specified Roberto Mello
  • Re: pg_publication_tables: return NULL attnames when no column list is specified Amit Kapila
  • Re: pg_publication_tables: return NULL attnames when no column list is specified Roberto Mello
  • Re: pg_publication_tables: return NULL attnames when no column list is specified David G. Johnston
  • Re: pg_publication_tables: return NULL attnames when no column list is specified Roberto Mello
• Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? shveta malik
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Amit Kapila
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Amit Kapila
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? shveta malik
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • RE: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Zhijie Hou (Fujitsu)
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Amit Kapila
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Amit Kapila
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? shveta malik
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Fujii Masao
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
  • Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion? Nisha Moond
• Re: POC: Parallel processing of indexes in autovacuum Bharath Rupireddy
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum SATYANARAYANA NARLAPURAM
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Alexander Korotkov
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum SATYANARAYANA NARLAPURAM
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Alexander Korotkov
  • Re: POC: Parallel processing of indexes in autovacuum Masahiko Sawada
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
  • Re: POC: Parallel processing of indexes in autovacuum SATYANARAYANA NARLAPURAM
  • Re: POC: Parallel processing of indexes in autovacuum Daniil Davydov
• RE: Patch for migration of the pg_commit_ts directory Hayato Kuroda (Fujitsu)
  • Re: Patch for migration of the pg_commit_ts directory ls7777
  • Re: Patch for migration of the pg_commit_ts directory ls7777
  • Re: Patch for migration of the pg_commit_ts directory ls7777
• Re: Refactor query normalization into core query jumbling Lukas Fittl
  • Re: Refactor query normalization into core query jumbling Michael Paquier
  • Re: Refactor query normalization into core query jumbling Lukas Fittl
  • Re: Refactor query normalization into core query jumbling Sami Imseih
  • Re: Refactor query normalization into core query jumbling Michael Paquier
  • Re: Refactor query normalization into core query jumbling Lukas Fittl
  • Re: Refactor query normalization into core query jumbling Sami Imseih
  • Re: Refactor query normalization into core query jumbling Michael Paquier
  • Re: Refactor query normalization into core query jumbling Sami Imseih
  • Re: Refactor query normalization into core query jumbling Lukas Fittl
  • Re: Refactor query normalization into core query jumbling Michael Paquier
  • Re: Refactor query normalization into core query jumbling Sami Imseih
  • Re: Refactor query normalization into core query jumbling Michael Paquier
  • Re: Refactor query normalization into core query jumbling Lukas Fittl
  • Re: Refactor query normalization into core query jumbling Sami Imseih
• Re: Make COPY format extendable: Extract COPY TO format implementations Sutou Kouhei
• Re: Skipping schema changes in publication Peter Smith
  • Re: Skipping schema changes in publication Amit Kapila
  • Re: Skipping schema changes in publication Shlok Kyal
  • Re: Skipping schema changes in publication shveta malik
  • Re: Skipping schema changes in publication Amit Kapila
  • Re: Skipping schema changes in publication Shlok Kyal
  • Re: Skipping schema changes in publication Peter Smith
  • Re: Skipping schema changes in publication shveta malik
  • Re: Skipping schema changes in publication Amit Kapila
  • Re: Skipping schema changes in publication Dilip Kumar
  • Re: Skipping schema changes in publication shveta malik
  • Re: Skipping schema changes in publication Peter Smith
  • Re: Skipping schema changes in publication vignesh C
  • Re: Skipping schema changes in publication Peter Smith
  • RE: Skipping schema changes in publication Hayato Kuroda (Fujitsu)
  • Re: Skipping schema changes in publication Peter Smith
  • Re: Skipping schema changes in publication Amit Kapila
  • Re: Skipping schema changes in publication vignesh C
  • Re: Skipping schema changes in publication Peter Smith
  • Re: Skipping schema changes in publication Amit Kapila
  • Re: Skipping schema changes in publication Peter Smith
  • Re: Skipping schema changes in publication vignesh C
  • Re: Skipping schema changes in publication Peter Smith
  • Re: Skipping schema changes in publication shveta malik
  • RE: Skipping schema changes in publication Zhijie Hou (Fujitsu)
  • Re: Skipping schema changes in publication Amit Kapila
  • Re: Skipping schema changes in publication vignesh C
  • Re: Skipping schema changes in publication Amit Kapila
  • RE: Skipping schema changes in publication Zhijie Hou (Fujitsu)
  • Re: Skipping schema changes in publication Amit Kapila
  • Re: Skipping schema changes in publication SATYANARAYANA NARLAPURAM
  • Re: Skipping schema changes in publication Shlok Kyal
  • Re: Skipping schema changes in publication shveta malik
• Re: Add comments about fire_triggers argument in ri_triggers.c Amit Langote
  • Re: Add comments about fire_triggers argument in ri_triggers.c Yugo Nagata
  • Re: Add comments about fire_triggers argument in ri_triggers.c Amit Langote
  • Re: Add comments about fire_triggers argument in ri_triggers.c Amit Langote
  • Re: Add comments about fire_triggers argument in ri_triggers.c surya poondla
  • Re: Add comments about fire_triggers argument in ri_triggers.c Yugo Nagata
• [Proposal] pg_stat_wal_records – per-record-type WAL generation statistics SATYANARAYANA NARLAPURAM
  • Re: [Proposal] pg_stat_wal_records – per-record-type WAL generation statistics Michael Paquier
  • Re: [Proposal] pg_stat_wal_records – per-record-type WAL generation statistics SATYANARAYANA NARLAPURAM
• Re: log XLogPrefetch stats at end of recovery Bharath Rupireddy
  • Re: log XLogPrefetch stats at end of recovery SATYANARAYANA NARLAPURAM
• Re: BM_IO_ERROR flag is lost in TerminateBufferIO due to order of operations in UnlockBufHdrExt Andres Freund
  • Re: BM_IO_ERROR flag is lost in TerminateBufferIO due to order of operations in UnlockBufHdrExt Yura Sokolov
  • Re: BM_IO_ERROR flag is lost in TerminateBufferIO due to order of operations in UnlockBufHdrExt Yura Sokolov
  • Re: BM_IO_ERROR flag is lost in TerminateBufferIO due to order of operations in UnlockBufHdrExt Yura Sokolov
  • Re: BM_IO_ERROR flag is lost in TerminateBufferIO due to order of operations in UnlockBufHdrExt Michael Paquier
  • Re: BM_IO_ERROR flag is lost in TerminateBufferIO due to order of operations in UnlockBufHdrExt Yura Sokolov
• Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • RE: Initial COPY of Logical Replication is too slow Hayato Kuroda (Fujitsu)
  • Re: Initial COPY of Logical Replication is too slow Amit Kapila
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re: Initial COPY of Logical Replication is too slow Marcos Pegoraro
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • RE: Initial COPY of Logical Replication is too slow Zhijie Hou (Fujitsu)
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re:Re: Initial COPY of Logical Replication is too slow 王好燕
  • Re: Initial COPY of Logical Replication is too slow Haoyan Wang
  • RE: Initial COPY of Logical Replication is too slow Hayato Kuroda (Fujitsu)
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • RE: Initial COPY of Logical Replication is too slow Hayato Kuroda (Fujitsu)
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re: Initial COPY of Logical Replication is too slow Amit Kapila
  • RE: Initial COPY of Logical Replication is too slow Zhijie Hou (Fujitsu)
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re: Initial COPY of Logical Replication is too slow Amit Kapila
  • Re: Initial COPY of Logical Replication is too slow Peter Smith
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re: Initial COPY of Logical Replication is too slow Amit Kapila
  • Re: Initial COPY of Logical Replication is too slow Masahiko Sawada
  • Re: Initial COPY of Logical Replication is too slow Amit Kapila
• Re: Fixes inconsistent behavior in vacuum when it processes multiple relations Michael Paquier
  • Re: Fixes inconsistent behavior in vacuum when it processes multiple relations Nathan Bossart
  • Re: Fixes inconsistent behavior in vacuum when it processes multiple relations Nathan Bossart
  • Re: Fixes inconsistent behavior in vacuum when it processes multiple relations Nathan Bossart
• Re: Track skipped tables during autovacuum and autoanalyze Michael Paquier
  • Re: Track skipped tables during autovacuum and autoanalyze Yugo Nagata
  • Re: Track skipped tables during autovacuum and autoanalyze Sami Imseih
  • Re: Track skipped tables during autovacuum and autoanalyze Yugo Nagata
  • Re: Track skipped tables during autovacuum and autoanalyze Yugo Nagata
  • Re: Track skipped tables during autovacuum and autoanalyze Sami Imseih
• Re: Adjust error message for CREATE STATISTICS to account for expressions Michael Paquier
  • Re: Adjust error message for CREATE STATISTICS to account for expressions John Naylor
  • Re: Adjust error message for CREATE STATISTICS to account for expressions Yugo Nagata
  • Re: Adjust error message for CREATE STATISTICS to account for expressions Dean Rasheed
  • Re: Adjust error message for CREATE STATISTICS to account for expressions Yugo Nagata
  • Re: Adjust error message for CREATE STATISTICS to account for expressions John Naylor
  • Re: Adjust error message for CREATE STATISTICS to account for expressions Yugo Nagata
  • Re: Adjust error message for CREATE STATISTICS to account for expressions Dean Rasheed
  • Re: Adjust error message for CREATE STATISTICS to account for expressions Yugo Nagata
  • Re: Adjust error message for CREATE STATISTICS to account for expressions John Naylor
  • Re: Adjust error message for CREATE STATISTICS to account for expressions Chao Li
• Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) David Rowley
  • 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) David Rowley
  • 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) David Rowley
  • 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) Alexander Lakhin
  • 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) 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) 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) Alexander Lakhin
  • Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) Andres Freund

• Earlier messages
• Later messages