Re: overriding current_timestamp

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: overriding current_timestamp
Date: 2012-02-27 19:39:27
Message-ID: 1330371567.7111.28.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On mån, 2012-02-27 at 08:48 -0800, David E. Wheeler wrote:
> On Feb 27, 2012, at 4:29 AM, Peter Eisentraut wrote:
>
> >> I create a "mock" schema, add the function to it, and then put it in the search_path ahead of pg_catalog.
> >
> > That doesn't work for current_timestamp and similar built-in functions,
> > because they are always mapped to the pg_catalog schema.
>
> I use it for NOW() all the time.

But it won't work for current_timestamp.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2012-02-27 19:40:55 Re: overriding current_timestamp
Previous Message Andres Freund 2012-02-27 19:37:24 Re: Command Triggers, patch v11