Re: [PATCH] Proposal for HIDDEN/INVISIBLE column - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: [PATCH] Proposal for HIDDEN/INVISIBLE column
Date
Msg-id 6aaa2eff-5c0a-06bb-e988-1a7c39d14ddc@xs4all.nl
Whole thread Raw
In response to Re: [PATCH] Proposal for HIDDEN/INVISIBLE column  (Gilles Darold <gilles@migops.com>)
Responses Re: [PATCH] Proposal for HIDDEN/INVISIBLE column  (Gilles Darold <gilles@migops.com>)
List pgsql-hackers
Op 27-10-2021 om 16:33 schreef Gilles Darold:
>>
>> - Fix documentation about some sgml tag broken.
>>
>>
>> About ROWTYPE generating an error when SELECT * INTO or RETURNING * INTO
>> is used with unexpanded column, I have kept things like that because it
>> is the normal behavior. I have checked on others database engine and
>> this is the same.1
> 
> 
> And finally I found the reason of the diff on compression.out and 
> collate.linux.utf8.out, new version v5 of the patch attached.
> 
 > [ 0001-hidden-column-v5.patch ]


This warning during compile from gcc 11.2:

pg_dump.c: In function ‘dumpTableSchema’:
pg_dump.c:16327:56: warning: comparison of constant ‘0’ with boolean 
expression is always true [-Wbool-compare]
16327 |                         if (tbinfo->attisunexpanded[j] >= 0)
       |                                                        ^~

Otherwise, build, make check, chekc-world are OK.  Also the pdf builds ok.

Thanks,

Erik Rijkers









pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Parameter for planner estimate of recursive queries
Next
From: Gilles Darold
Date:
Subject: Re: [PATCH] Proposal for HIDDEN/INVISIBLE column