Re: [HACKERS] Updating column on row update

Hannu Krosing <hannu@2ndquadrant.com>

From: Hannu Krosing <hannu@2ndQuadrant.com>
To: Thom Brown <thombrown@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Craig Ringer <craig@postnewspapers.com.au>, Scott Marlowe <scott.marlowe@gmail.com>, PGSQL Mailing List <pgsql-general@postgresql.org>, pgsql-hackers@postgresql.org
Date: 2009-11-24T11:06:46Z
Lists: pgsql-hackers, pgsql-general
On Tue, 2009-11-24 at 09:46 +0000, Thom Brown wrote:
> 2009/11/24 Hannu Krosing <hannu@2ndquadrant.com>
>         On Sun, 2009-11-22 at 18:51 -0500, Tom Lane wrote:
>         > Craig Ringer <craig@postnewspapers.com.au> writes:
>         > > I do think this comes up often enough that a built-in
>         trigger "update
>         > > named column with result of expression on insert" trigger
>         might be
>         > > desirable.
>         >
>         > There's something of the sort in contrib already, I believe,
>         though
>         > it's so old it still uses abstime :-(
>         
>         
>         What's wrong with abstime ?
>         
>         it is valid for timestamps up to 2038-01-19 and it's on-disk
>         size
>         smaller than other timestamp options
>         
> 
> But it's very very deprecated and could be removed at any time.  It's
> been so for years now, and I wouldn't want to *start* using something
> which is deprecated.
> 
> Thom

I'd expect it to have an afterlife as a separately maintained type
somewhere for those who care about data sizes, similar other space
savers like ip4 type.


-- 
Hannu Krosing   http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability 
   Services, Consulting and Training