| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> | 
|---|---|
| To: | "val(dot)janeiko(at)gmail(dot)com" <val(dot)janeiko(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> | 
| Subject: | Re: BUG #16430: Sequence with cache > 1 makes it increment by number specified as cache | 
| Date: | 2020-05-12 15:47:35 | 
| Message-ID: | CAKFQuwYeiR4WUg_3+=qrigDF=BfW1bsfD1tGf_Xs0Mj-R5koeQ@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-bugs | 
On Tuesday, May 12, 2020, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference:      16430
> Logged by:          Valentinas
> Email address:      val(dot)janeiko(at)gmail(dot)com
> PostgreSQL version: 12.2
> Operating system:   Alpine (container)
> Description:
>
> When using Sequence inside a plpgsql function called using SELECT func()
> using Npgsql library a sequence is incremented by the value specified in
> CACHE.
>
>
That is a perfectly valid outcome per the meaning and documented usage of
cache in the server.
> Additionally if CACHE is set to > 80000 (e.g. 100000) the query always
> returns 0.
>
Interesting...probably worth looking into even if a cache value that large
doesn’t make much sense usually.  Doing and posting some tests using just
sql and psql would be a good start in isolating where the discrepancy lies.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2020-05-12 22:15:48 | Re: BUG #16430: Sequence with cache > 1 makes it increment by number specified as cache | 
| Previous Message | Sergei Kornilov | 2020-05-12 15:44:24 | Re: BUG #16430: Sequence with cache > 1 makes it increment by number specified as cache |