| From: | Thom Brown <thombrown(at)gmail(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Scott Marlowe <scott(dot)marlowe(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 09:46:56 |
| Message-ID: | bddc86150911240146l645825f2h568026460f92db4f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
2009/11/24 Hannu Krosing <hannu(at)2ndquadrant(dot)com>
> 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
>
>
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Jas | 2009-11-24 09:50:35 | Re: Strange performance degradation |
| Previous Message | Hannu Krosing | 2009-11-24 08:47:46 | Re: [HACKERS] Updating column on row update |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-11-24 10:10:48 | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |
| Previous Message | Daniel Farina | 2009-11-24 08:57:02 | Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION |