| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Thom Brown <thombrown(at)gmail(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Updating column on row update |
| Date: | 2009-11-24 08:47:46 |
| Message-ID: | 1259052466.30357.64.camel@hvost1700 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Sun, 2009-11-22 at 18:51 -0500, Tom Lane wrote:
> Craig Ringer <craig(at)postnewspapers(dot)com(dot)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
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2009-11-24 09:46:56 | Re: [HACKERS] Updating column on row update |
| Previous Message | Bill Todd | 2009-11-24 02:09:11 | How identify a long running transaction |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2009-11-24 08:54:26 | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |
| Previous Message | Hannu Krosing | 2009-11-24 08:38:37 | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |