In PostgreSQL, the sign()
function is used to indicate the sign of its argument.
It doesn’t simply return the actual sign. Rather, it returns -1 for negative numbers, 0 for zero, and 1 for positive numbers.
Continue readingIn PostgreSQL, the sign()
function is used to indicate the sign of its argument.
It doesn’t simply return the actual sign. Rather, it returns -1 for negative numbers, 0 for zero, and 1 for positive numbers.
Continue readingIn PostgreSQL, clock_timestamp()
is a non-SQL-standard time function that returns the current date and time.
An important consideration of this function is that its result changes throughout the execution of a statement. Therefore, you could get a different result in different parts of the statement if you call the function multiple times within a single statement.
Continue readingIn PostgreSQL, the cbrt()
function returns the cube root of its argument.
The cube root of a number x is a number y such that y3 = x.
Continue readingIn PostgreSQL, the sqrt()
function returns the square root of its argument.
The square root of a number x is the number y such that y2 = x.
Continue readingIn PostgreSQL, the abs()
function returns the absolute value of its argument.
The absolute value means how far the number is away from zero. Therefore, the absolute value of 7 is 7, and the absolute value of -7 is also 7.
Therefore, any negative values passed to abs()
are returned as positive values. Positive values and zero are returned unchanged.
In SQL Server, you can use the WAITFOR
statement to delay the execution of a batch, stored procedure, or transaction.
It works similar to MySQL‘s sleep()
function.
Actually, it’s probably more like a combination of Postgres‘s three “sleep” functions: pg_sleep()
, pg_sleep_for()
, and pg_sleep_until()
.
I say this, because SQL Server’s WAITFOR
statement gives you the option of specifying either a time delay, or an actual fixed time before execution continues.
In PostgreSQL, you can use the pg_sleep()
function to delay execution for a given number of seconds.
It makes the current session’s process sleep until the specified number of seconds have elapsed. It works similar to MySQL‘s sleep()
function, and also TSQL‘s waitfor
statement in SQL Server.
The pg_sleep()
function accepts a double precision argument, so you can also specify fractional-second delays.
The sleep delay will be at least as long as specified. However, it could be longer depending on factors such as server load, as well as your platform’s effective resolution of the sleep interval.
Continue readingIn PostgreSQL, you can use the pg_sleep_for()
function to delay execution for a given interval.
It makes the current session’s process sleep until the specified interval has elapsed.
The sleep delay will be at least as long as specified. However, it could be longer depending on factors such as server load, as well as your platform’s effective resolution of the sleep interval.
Continue readingIn PostgreSQL, you can use the pg_sleep_until()
function to delay execution until a specified timestamp.
This is useful for when a specific wake-up time is desired.
Note that pg_sleep_until
is not guaranteed to wake up exactly at the specified time, but it will not wake up any earlier.
In PostgreSQL, the setseed()
function sets the seed for subsequent random()
and random_normal()
calls (value between -1.0 and 1.0, inclusive).
The random()
function generates a pseudo-random number using a simple linear congruential algorithm. The random_normal()
function generates a normally-distributed random number.
If setseed()
is called, the results of subsequent random()
and random_normal()
calls in the current session are repeatable by re-issuing setseed()
with the same argument.