Re: Cannot find hstore operator

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Paul van der Linden <paul(dot)doskabouter(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Cannot find hstore operator
Date: 2022-01-23 15:22:06
Message-ID: 1585432.1642951326@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Paul van der Linden <paul(dot)doskabouter(at)gmail(dot)com> writes:
> Thanks for the clarification, but giving up performance is a no-go for us.
> Also I have my concerns about shemaqualifying each and every use of the ->
> operator, there are really a lot of them in my functions and it would
> severely impact readability.
> Are these the only 2 solutions possible?

As of v14 you could use SQL-style function definitions, so that the
operator is parsed at function definition time instead of runtime.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Игорь Выскорко 2022-01-24 07:48:56 Broken logical replication
Previous Message David G. Johnston 2022-01-23 15:20:55 Re: Cannot find hstore operator