We're seeing this from Jira 9.4.8 LTS and Confluence 7.19.16 LTS in the postgresql logs

I am seeing this Postgresql error in Confluence 7.15.X, as well.

Thank you for the support, this issue is frustrating.

What I don't understand is why Jira has to check every hour.  Isn't it enough to check once at startup?  That would be a lot better.  If the PostgreSQL database wasn't located in AWS when Jira started up, it cannot suddenly move to AWS while Jira is still running.  Can an AWS PostgreSQL database change versions without restarting Jira?

I guess we can conclude by now that atlASSian JiRa either bluntly ignores this from their paying customers or really simply do not have any clue on how to approach this easy little fix. 

( e.g.: CHECK if aurora_version exists and then handle that effing situation in stead of constantly whining in the log about your own lack of coding skills, @Atlassian ?      Sorry if you're offended, but you've had quite a lot more than ample time to proof us wrong here.    ) 

November 2022, just started seeing this error when we upgraded from Jira 9.1 to 9.3.1.  Since Jira dropped support for MySQL 5.7 we had to switch to a PostgreSQL database, and now we get this annoying error message constantly.

We scan our database logs for real errors and notify developers and IT security when we see something unusual.  Now its full of fake errors caused by Jira.  This error may be harmless to Jira but it is causing problems for us.

function aurora_version() does not exist at character 8

Aug. 2022 still no resolution

@devcell    :  I guess you could create a fake function aurora_version() which just returns:      'ATLASSIAN CODERS HAVENT GOT A CLUE HOW TO FIX THIS SCHEIDT'    and see what happens ? 
They have really worked hard and long now, ignoring this annoyance.

Have a ball with this, Atlassian. It's free.WAIT - no, I'll have to charge you DataCenterDeluxe pricing for this, due to recent management decisions at my executive level. 

If you use it, you'll owe me a gazillion bucks - and that's including the 98% discount I give for new global Corporations.  
{{}}

create or replace function aurora_version() returns table  ( jiracrap text) 
as
$$
  SELECT ' Atlassian have no clue on how to fix this if you do not ' as JiraCrap
  FROM dual
    UNION ALL
  SELECT ' run on an AWS Aurora Postgres ' as JiraCrap
  FROM dual;
$$
language sql; 

You're welcome  

How do I solve this problem?
Is this a jira issue or a postgres issue?
I am using postgres 11 version based on docker.

// code placeholder
postgres-atlassian    | 2020-12-04 06:57:36.405 UTC [48339] STATEMENT:  select 1
postgres-atlassian    | 2020-12-04 06:57:40.030 UTC [48025] ERROR:  function aurora_version() does not exist at character 8
postgres-atlassian    | 2020-12-04 06:57:40.030 UTC [48025] HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
postgres-atlassian    | 2020-12-04 06:57:40.030 UTC [48025] STATEMENT:  select AURORA_VERSION() as aurora_version
postgres-atlassian    | 2020-12-04 06:59:35.366 UTC [48537] ERROR:  function aurora_version() does not exist at character 8
postgres-atlassian    | 2020-12-04 06:59:35.366 UTC [48537] HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
postgres-atlassian    | 2020-12-04 06:59:35.366 UTC [48537] STATEMENT:  select AURORA_VERSION() as aurora_version
postgres-atlassian    | 2020-12-04 06:59:35.367 UTC [48537] ERROR:  current transaction is aborted, commands ignored until end of transaction block
postgres-atlassian    | 2020-12-04 06:59:35.367 UTC [48537] STATEMENT:  select 1
postgres-atlassian    | 2020-12-04 07:57:12.074 UTC [54180] ERROR:  function aurora_version() does not exist at character 8
postgres-atlassian    | 2020-12-04 07:57:12.074 UTC [54180] HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
postgres-atlassian    | 2020-12-04 07:57:12.074 UTC [54180] STATEMENT:  select AURORA_VERSION() as aurora_version
postgres-atlassian    | 2020-12-04 07:57:15.485 UTC [54460] ERROR:  function aurora_version() does not exist at character 8
postgres-atlassian    | 2020-12-04 07:57:15.485 UTC [54460] HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
postgres-atlassian    | 2020-12-04 07:57:15.485 UTC [54460] STATEMENT:  select AURORA_VERSION() as aurora_version
postgres-atlassian    | 2020-12-04 07:57:15.490 UTC [54460] ERROR:  current transaction is aborted, commands ignored until end of transaction block

It looks as if you, Atlassian, should teach your  set-analytics-bot how to perform  "Triage"
It really looks as if that "employee" is the only one working (and it's working a lot) on this ticket  

Same here