Message-ID: <f51661770a45ce6c28aa2a39badf2e7769853e42.camel@cybertec.at>
Subject: Re: Pseudocode / Pseudo-Types
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: soumik.bhattacharjee@kpn.com, pgsql-admin@postgresql.org
Date: Mon, 15 Mar 2021 15:14:34 +0100
In-Reply-To: <7af47a45b89d4ce2bd4a03179e6bb373@kpn.com>
References: <7af47a45b89d4ce2bd4a03179e6bb373@kpn.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/f51661770a45ce6c28aa2a39badf2e7769853e42.camel%40cybertec.at>
Precedence: bulk

On Mon, 2021-03-15 at 13:55 +0000, soumik.bhattacharjee@kpn.com wrote:
> Has anybody has a use case for using Pseudocode / Pseudo-Types?
> 
> Any inputs will be helpful and if any reference sites to check some example use cases are also good to start with.
> 
> Thanks in advance...

Pseudocode, as in

  while (there is something to do)
     process_one_item();

is a tool to write down an algorithm in a way that is easy for
programmers to understand.

Pseudo-types, as in
https://www.postgresql.org/docs/current/datatype-pseudo.html
are something entirely different.

Here is a useful example:

CREATE FUNCTION successor(anyelement) RETURNS anyelement
   LANGUAGE sql AS 'SELECT $1 + 1';

SELECT successor(41);

 successor 
-----------
        42
(1 row)

SELECT successor(current_date);

 successor  
------------
 2021-03-16
(1 row)

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com