Re: improve DEBUG1 logging of parallel workers for CREATE INDEX?

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: improve DEBUG1 logging of parallel workers for CREATE INDEX?
Date: 2025-02-03 20:29:03
Message-ID: CAA5RZ0tW=9qE6zLxuSQBimG_JjHg-Z0PK7dKn3r21NH9_Q+Rwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At this point I am planning on withdrawing this patch
from the March commitfest. I don't think fixing the REINDEX
debug1 output makes a whole lot of sense. I still think more logging
for (CREATE|ALTER) (INDEX|TABLE) will be a good to have but there
needs to be more discussion about the best approach.

Regards,

Sami

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-02-03 20:36:21 Re: pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value.
Previous Message Nathan Bossart 2025-02-03 20:27:07 Re: why there is not VACUUM FULL CONCURRENTLY?