Re: Odd behavior with 'currval'

From: Steven Hirsch <snhirsch(at)gmail(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Odd behavior with 'currval'
Date: 2018-02-08 21:22:39
Message-ID: alpine.DEB.2.20.1802081620300.5809@z87
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 8 Feb 2018, David G. Johnston wrote:

> On Thu, Feb 8, 2018 at 12:54 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>  The only 'currval' procedure is the one defined at installation (in public).
>
>
> ​So, the installed version of currval would be defined in "pg_catalog", not "public" ...

??

All I can tell you is that when I connect from dbVisualizer and open the
twisty under 'main.procedures' I see 100+ functions that are intrinsic to
pgsql - currval() included. I have almost no experience writing pgsql
procs and absolutely never installed anything that would override the base
function.

--

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2018-02-08 21:27:38 Re: Odd behavior with 'currval'
Previous Message Igor Korot 2018-02-08 20:57:37 Re: DOW is 0-based?