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 16:51:20
Message-ID: 0E379B0D-EEFA-45FB-AC60-23F760B8D338@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Feb 27, 2012, at 4:29 AM, Peter Eisentraut wrote:

>> Sorry, starting at slide 480.
>
> That presentation only goes to slide 394.

Crimony, sorry, this presentation:

http://www.slideshare.net/justatheory/test-drivern-database-development

Note that I put pg_catalog at the end of the search_path, so that my mocked function will be found before it gets found in pg_catalog. If you don't add it to the end, it's implicitly the first item in the search path.

Best,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-02-27 16:59:12 Re: [PATCH] Cleanup: use heap_open/heap_close consistently
Previous Message David E. Wheeler 2012-02-27 16:48:53 Re: overriding current_timestamp