Search Postgresql Archives

Re: Odd behavior with 'currval'

Subject: Re: Odd behavior with 'currval'
From: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Date: Thu, 8 Feb 2018 12:55:20 -0700
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <CAKFQuwYCK1qXkmcO2e7az5ZDX=y5xBvJT-29zQNFSXuuvR1_pQ@mail.gmail.com>
References: <alpine.DEB.2.20.1802081050480.5809@z87> <CA+bJJbw-V2_gCUkbFTAn5USXZ9jtHrzh9vVMbB7mwg_yrMDyvQ@mail.gmail.com> <alpine.DEB.2.20.1802081243130.5809@z87> <CAKFQuwYOid4vqN6abpxS=VrrYnt3PBnmvSF+Lk317cuL_jW32w@mail.gmail.com> <alpine.DEB.2.20.1802081443480.5809@z87> <CAKFQuwYCK1qXkmcO2e7az5ZDX=y5xBvJT-29zQNFSXuuvR1_pQ@mail.gmail.com>

On Thu, Feb 8, 2018 at 12:54 PM, David G. Johnston <david.g.johnston@xxxxxxxxx> 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" ...

David J.

References:
- Odd behavior with 'currval'
  - From: Steven Hirsch
- Re: Odd behavior with 'currval'
  - From: Francisco Olarte
- Re: Odd behavior with 'currval'
  - From: Steven Hirsch
- Re: Odd behavior with 'currval'
  - From: David G. Johnston
- Re: Odd behavior with 'currval'
  - From: Steven Hirsch
- Re: Odd behavior with 'currval'
  - From: David G. Johnston