Re: Some more information_schema issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Some more information_schema issues
Date: 2003-10-17 13:53:51
Message-ID: 22212.1066398831@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> True. Btw., is there a particular value in pg_get_constraintdef always
> printing double pairs of parentheses for CHECK constraints?

No, but it will require some restructuring of the code to get rid of it
safely (where "safely" is defined as "never omitting any parentheses
that *are* necessary"). For the moment I'm willing to live with the
ugliness. You could consider pretty-printing (pass true to
pg_get_constraintdef) if you think visual appeal is better than
assured correctness.

>> There are several views that display pg_type.typname directly. I wonder
>> whether any of these ought to be using format_type() instead.

> typname is used in those contexts where the type name appears together
> with a schema name. In those cases you cannot use the result of
> format_type.

Okay, fair enough.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shridhar Daithankar 2003-10-17 13:55:13 Re: Some thoughts about i/o priorities and throttling vacuum
Previous Message Andrew Sullivan 2003-10-17 13:50:07 Re: Some thoughts about i/o priorities and throttling vacuum