[OT] newsreader issue? (Was: bytea encode performance issues) - Mailing list pgsql-general

From Lew
Subject [OT] newsreader issue? (Was: bytea encode performance issues)
Date
Msg-id zpadnXbQLsIqJwjVnZ2dnUVZ_vqdnZ2d@comcast.com
Whole thread Raw
In response to Re: bytea encode performance issues  (Sim Zacks <sim@compulab.co.il>)
Responses Re: [OT] newsreader issue? (Was: bytea encode performance issues)
Re: [OT] newsreader issue? (Was: bytea encode performance issues)
Re: [OT] newsreader issue? (Was: bytea encode performance issues)
List pgsql-general
Sim Zacks wrote:
> (quoting someone:)
>> That LIKE operator is probably your problem. An unbounded LIKE like that
>> (with a wildcard on both sides) means no index can be used, hence you
>> get a sequential scan.

Was the message to which you responded posted to the newsgroup?  It isn't
appearing in my newsreader.

Who wrote the message you quoted (you failed to cite the source)?

--
Lew

pgsql-general by date:

Previous
From: Rob Adams
Date:
Subject: recovery via base + WAL replay failure
Next
From: "Scott Marlowe"
Date:
Subject: Re: [OT] newsreader issue? (Was: bytea encode performance issues)