Search Postgresql Archives
functions with side effect
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: functions with side effect
From
: Torsten Förtsch <tfoertsch123@xxxxxxxxx>
Date
: Thu, 19 Jul 2018 16:15:28 +0200
Hi,
assuming
SELECT nextval('s'), currval('s');
or
SELECT * FROM (VALUES (nextval('s'), currval('s'))) t;
is there any guarantee that the 2 output values are the same?
Thanks,
Torsten
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Follow-Ups
:
Re: functions with side effect
From:
Adrian Klaver
Re: functions with side effect
From:
Laurenz Albe
Prev by Date:
Incorrect description of the WITH CHECK in the row security can lead to the security issue
Next by Date:
Re: functions with side effect
Previous by thread:
Incorrect description of the WITH CHECK in the row security can lead to the security issue
Next by thread:
Re: functions with side effect
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]