Horton

Re: [HACKERS] generated columns

Pavel Stehule <pavel.stehule@gmail.com>

View thread View on postgr.es
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>, Sergei Kornilov <sk@zsrv.org>, Michael Paquier <michael.paquier@gmail.com>, Jaime Casanova <jaime.casanova@2ndquadrant.com>
Date: 2019-01-16T08:27:16Z
Lists: pgsql-hackers 
st 16. 1. 2019 v 9:26 odesílatel Peter Eisentraut <
peter.eisentraut@2ndquadrant.com> napsal:

> On 15/01/2019 08:18, Pavel Stehule wrote:
> > I would to have a mechanism for safe replacement of triggers of type
> >
> > if TG_TYPE = 'INSERT' THEN
> >   NEW.inserted := CURRENT_TIMESTAMP;
> > ELSE IF TG_TYPE = 'UPDATE' THEN
> >   NEW.updated := CURRENT_TIMESTAMP;
> >  ..
>
> That kind of use is probably better addressed with a temporal facility.
>

yes. I am looking for this functionality in Postgres

Pavel


> --
> Peter Eisentraut              http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

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