Re: Print baserestrictinfo for varchar fields

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Donald Dong <xdong(at)csumb(dot)edu>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Print baserestrictinfo for varchar fields
Date: 2019-06-04 01:37:59
Message-ID: 20190604013759.GG1529@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 03, 2019 at 01:37:22AM -0400, Tom Lane wrote:
> It's hard to muster much enthusiasm for extending print_expr(),
> considering how incomplete and little-used it is. I'd rather
> spend effort on ripping it out in favor of using the far more
> complete, and better-tested, code in ruleutils.c.

If it is possible to get the same amount of coverage when debugging
the planner, count me in. Now it seems to me that we'd still require
some work to get the same level of information as for range table
entry kinds..
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashwin Agrawal 2019-06-04 01:41:35 Re: Comment typo in tableam.h
Previous Message Michael Paquier 2019-06-04 01:27:00 Re: Confusing error message for REINDEX TABLE CONCURRENTLY