Re: information_schema.view attgenerated - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: information_schema.view attgenerated
Date
Msg-id 782d873b-5e18-4de4-8e5c-ab619f59d71a@eisentraut.org
Whole thread Raw
In response to information_schema.view attgenerated  (jian he <jian.universality@gmail.com>)
List pgsql-hackers
On 16.09.24 06:12, jian he wrote:
> hi.
> one minor issue in src/backend/catalog/information_schema.sql
> /*
>   * 6.22
>   * COLUMNS view
>   */
> CREATE VIEW columns ....
> 
> 
> CAST(CASE WHEN a.attgenerated = '' THEN pg_get_expr(ad.adbin,
> ad.adrelid) END AS character_data) AS column_default,
> can change to
> CAST(CASE WHEN a.attgenerated = '' AND a.atthasdef THEN
> pg_get_expr(ad.adbin, ad.adrelid) END AS character_data) AS
> column_default,
> 
> 
> CAST(CASE WHEN a.attgenerated <> '' THEN 'ALWAYS' ELSE 'NEVER' END AS
> character_data) AS is_generated,
> can change to
> CAST(CASE WHEN a.attgenerated <> '' AND a.atthasdef THEN 'ALWAYS' ELSE
> 'NEVER' END AS character_data) AS is_generated,
> 
> CAST(CASE WHEN a.attgenerated <> '' THEN pg_get_expr(ad.adbin,
> ad.adrelid) END AS character_data) AS generation_expression,
> can change to
> CAST(CASE WHEN a.attgenerated <> '' AND a.atthasdef THEN
> pg_get_expr(ad.adbin, ad.adrelid) END AS character_data) AS
> generation_expression,
> 
> 
> i guess, it will have some minor speed up, also more accurate.

I'm having a hard time interpreting this report.  Could you be more 
clear about what is the existing code, and what is the code you are 
proposing as new.?




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: define pg_structiszero(addr, s, r)
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] WIP: replace method for jsonpath