Re: Cannot find hstore operator

From: Paul van der Linden <paul(dot)doskabouter(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Cannot find hstore operator
Date: 2022-01-24 09:17:40
Message-ID: CAEC-EqDzHDqd6T1NDKTHMYo23MQPYBBQZ=p8CZx-fGBeF1+Wcg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks, works perfectly!

On Sun, Jan 23, 2022 at 4:22 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2022-01-24 09:55:00 Re: Cannot find hstore operator
Previous Message Игорь Выскорко 2022-01-24 07:48:56 Broken logical replication