Re: overriding current_timestamp

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: overriding current_timestamp
Date: 2012-02-27 19:44:03
Message-ID: FCAA10CA-E87D-4166-9FA1-16117EEA9AF7@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Feb 27, 2012, at 11:43 AM, Peter Eisentraut wrote:

>> Why not? Not challenging your assertion here, just curious why it’s different.
>
> Because it's not actually a function, it's hardcoded in the grammar to
> call pg_catalog.now().

Ah, I see. Pity.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Lentfer 2012-02-27 20:24:11 Re: swapcache-style cache?
Previous Message Peter Eisentraut 2012-02-27 19:43:05 Re: overriding current_timestamp