Built-in functions
Last updated
Last updated
Aggregate functions compute a single result value from a set of input values. ().
Notes: PostgreSQL and Snowflake may show different precision/decimals due to data type rounding/formatting.
Notes: PostgreSQL defaults to UTC; the Snowflake function requires explicit UTC specification. Therefore, it will be added as the target timezone.
Notes: Invalid date part formats are translated to Snowflake-compatible formats.
Notes:
PostgreSQL treats newline, tab, and carriage return characters literally; Snowflake interprets them.
A JSON literal and dot-separated path are required to access nested objects in the Snowflake function.
Paths with spaces in variables must be quoted.
Notes: Snowflake and PostgreSQL handle SPLIT_PART differently with case-insensitive collations.
Notes: Snowflake partially supports this function. PostgreSQL's SUBSTRING, with a non-positive start_position, calculates start_position + number_characters (returning '' if the result is non-positive). Snowflake's behavior differs.
Notes: PostgreSQL uses keywords (BOTH, LEADING, TRAILING) for trim; Snowflake uses TRIM, LTRIM, RTRIM.
Notes: AVG rounding/formatting can vary by data type between PostgreSQL and Snowflake.
Notes: ORDER BY is mandatory in Snowflake; missing clauses are replaced with ORDER BY 1.
Notes: Snowflake needs ORDER BY; missing clauses get ORDER BY <expr>.
Notes: Snowflake needs ORDER BY; missing clauses get ORDER BY <expr>.
Notes: PostgreSQL allows constant or expression offsets; Snowflake allows only constant offsets.
Notes: ORDER BY is mandatory in Snowflake; missing clauses are replaced with ORDER BY 1.
Notes: ORDER BY is mandatory in Snowflake; missing clauses are replaced with ORDER BY 1.
Notes: Rounding varies between platforms.
Notes: ORDER BY is mandatory in Snowflake; missing clauses are replaced with ORDER BY 1.
Notes: Snowflake does not allow the use of date types, while PostgreSQL does. (See ).
(expression)
(expression)
(expression)
(expression)
(expression)
(expression)
(expression)
(expression)
( value [, ...] )
( expression, expression, ... )
( value [, ...] )
( <expr1> [, <expr2> ... ] )
( value [, ...] )
( <expr1> [, <expr2> ... ])
Notes: PostgreSQL's NULLIF ignores trailing spaces in some string comparisons, unlike Snowflake. Therefore, the transformation adds RTRIM for equivalence.
Data type formatting functions provide an easy way to convert values from one data type to another. For each of these functions, the first argument is always the value to be formatted and the second argument contains the template for the new format. ().
Notes: Snowflake's support for this function is partial (see ).
Notes: Snowflake's TO_DATE fails on invalid dates like '20010631' (June has 30 days), unlike PostgreSQL's lenient TO_DATE. Use TRY_TO_DATE in Snowflake to handle these cases by returning NULL. (see , ).
( <source_tz> , <target_tz> , <source_timestamp_ntz> )
( <target_tz> , <source_timestamp> )
Notes: this function is partially supported by Snowflake. (See ).
Notes: Part-time or Date time supported: DAY, DOW, DOY, EPOCH, HOUR, MINUTE, MONTH, QUARTER, SECOND, WEEK, YEAR.
PostgreSQL timestamps default to microsecond precision (6 digits); Snowflake defaults to nanosecond precision (9 digits). Adjust precision as needed using ALTER SESSION (e.g., ALTER SESSION SET TIMESTAMP_OUTPUT_FORMAT = 'YYYY-MM-DD HH24:MI:SS.FF2';). Precision loss may occur depending on the data type used.
Since some formats are incompatible with Snowflake, adjusting the account parameters might maintain functional equivalence between platforms.
String functions process and manipulate character strings or expressions that evaluate to character strings. ().
/
Notes: the results may vary between platforms (See ).
(string)
('"', string, '"')
Notes: This function includes a parameters argument that enables the user to interpret the pattern using the Perl Compatible Regular Expression (PCRE) dialect, represented by the p value, this is removed to avoid any issues. (See , , ).
(string, substring )
( <expr1> IN <expr> )
Notes: ORDER BY is mandatory in Snowflake; missing clauses are replaced with ORDER BY 1. (See ).
: Date or time format is not supported in Snowflake.
: Parameter is not a literal value, transformation could not be fully applied
: Function syntactically supported by Snowflake but may have functional differences.
: Regexp_Substr Function only supports POSIX regular expressions.
: The use of the COLLATE column constraint has been disabled for this pattern-matching condition.