Horton

Re: [HACKERS] generated columns

Corey Huinker <corey.huinker@gmail.com>

View thread View on postgr.es
From: Corey Huinker <corey.huinker@gmail.com>
To: michael@paquier.xyz
Cc: peter.eisentraut@2ndquadrant.com, pgsql-hackers@postgresql.org, michael.paquier@gmail.com, jaime.casanova@2ndquadrant.com
Date: 2018-11-15T16:48:52Z
Lists: pgsql-hackers 
>
> > 3. Radical alternative: Collapse everything into one new column.  We
> > could combine atthasdef and attgenerated and even attidentity into a new
> > column.  (Only one of the three can be the case.)  This would give
> > client code a clean break, which may or may not be good.  The
> > implementation would be uglier than #1 but probably cleaner than #2.  We
> > could also get 4 bytes back per pg_attribute row.
> >
> > I'm happy with the current choice #1, but it's worth thinking about.
>
> #3 looks very appealing in my opinion as those columns have no overlap,
> so it would take five possible values:
>

Could the removed columns live on...as generated-always columns?

Commits

  1. Generated columns

  2. Add walreceiver API to get remote server version

  3. Add pg_partition_tree to display information about partitions

  4. pg_restore: Augment documentation for -N option

  5. Change delimiter used for display of NextXID