On Sonntag 13 September 2009 Michael Monnerie wrote: > On Donnerstag 10 September 2009 Tom Lane wrote: > > There has *never* been a Postgres release that accepted bytea ILIKE > > something. I'm not sure what you were really doing before, but > > that wasn't it. > > You're right: That query was generated on a specific search, and > doesn't work. It's a bug that needs a fix. > > I currently have no idea how to cast bytea to text. For this purpose > of searching through mails, it would be enough for postgres to treat > the bytea as text, and just search through it. You can only find > ascii chars then, but that's a limitation one can live with. The only > other way would be to retrieve the whole stuff and search within a C > program, but that would mean retrieving a lot of data from the DB > that's not needed - bad for performance. Is there no "override" to > ignore bytea encoding and search it ascii-like? Ping? mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4 -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
