| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | thomas(dot)munro(at)gmail(dot)com |
| Cc: | nagata(at)sraoss(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org, kgrittn(at)gmail(dot)com |
| Subject: | Re: Implementing Incremental View Maintenance |
| Date: | 2019-07-08 08:04:38 |
| Message-ID: | 20190708.170438.2065860734679356276.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> As for how to make internal columns invisible to SELECT *, previously
> there have been discussions about doing that using a new flag in
> pg_attribute:
>
> https://www.postgresql.org/message-id/flat/CAEepm%3D3ZHh%3Dp0nEEnVbs1Dig_UShPzHUcMNAqvDQUgYgcDo-pA%40mail.gmail.com
Now that I realized that there are several use cases for invisible
columns, I think this is the way what we shoud go for.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-07-08 08:05:35 | Re: Replication & recovery_min_apply_delay |
| Previous Message | Michael Paquier | 2019-07-08 07:57:40 | Re: Add parallelism and glibc dependent only options to reindexdb |