Re: Is it worth adding Assert(false) for unknown paths in print_path()?

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
Subject: Re: Is it worth adding Assert(false) for unknown paths in print_path()?
Date: 2023-09-28 14:55:33
Message-ID: CAApHDvoCA3pqsyh7+XuF915-3OUiQmcnoQJSB=tD9bvL=tqbWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 29 Sept 2023 at 03:23, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> FWIW, I'd argue for dropping print_path rather than continuing to
> maintain it. I never use it, finding pprint() to serve the need
> better and more reliably.

Then perhaps we just need to open a thread with an appropriate subject
to check if anyone finds it useful and if we don't get any response
after some number of weeks, just remove it from master.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-09-28 15:25:04 Re: Eliminate redundant tuple visibility check in vacuum
Previous Message Tom Lane 2023-09-28 14:28:59 Re: Allow deleting enumerated values from an existing enumerated data type