Re: [HACKERS] generated columns

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Sergei Kornilov <sk(at)zsrv(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>
Subject: Re: [HACKERS] generated columns
Date: 2019-01-16 08:27:16
Message-ID: CAFj8pRBx8GFxWuZxyJ67Et3WcnXOYNJH-twEWN_Sw+joZN6_uw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

st 16. 1. 2019 v 9:26 odesílatel Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)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
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2019-01-16 08:29:25 Re: New vacuum option to do only freezing
Previous Message Michael Paquier 2019-01-16 08:27:05 Re: [HACKERS] REINDEX CONCURRENTLY 2.0