Search Postgresql Archives

Re: parray_gin and \d errors in PG10

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: parray_gin and \d errors in PG10
From: Tom Lane <tgl@xxxxxxxxxxxxx>
Date: Sun, 22 Oct 2017 16:48:19 -0400
Cc: pgsql-general@xxxxxxxxxxxxxx
Comments: In-reply-to Tom Lane <tgl@xxxxxxxxxxxxx> message dated "Sun, 22 Oct 2017 15:13:47 -0400"
In-reply-to: <28947.1508699627@sss.pgh.pa.us>
References: <20171022181525.GA21884@telsasoft.com> <26962.1508697372@sss.pgh.pa.us> <20171022184114.GI7575@telsasoft.com> <28947.1508699627@sss.pgh.pa.us>

I wrote:
> Or maybe what we should do is to avoid @> in favor of using
> ('d' = any(stxkind))

Pushed that way.

			regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- parray_gin and \d errors in PG10
  - From: Justin Pryzby
- Re: parray_gin and \d errors in PG10
  - From: Tom Lane
- Re: parray_gin and \d errors in PG10
  - From: Justin Pryzby
- Re: parray_gin and \d errors in PG10
  - From: Tom Lane

Prev by Date: Re: tgrm index for word_similarity
Next by Date: Backup strategy using 'wal_keep_segments'
Previous by thread: Re: parray_gin and \d errors in PG10
Next by thread: Backup strategy using 'wal_keep_segments'
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux