Re: [SQL] Invalid Unicode Character Sequence found

[Markus Bertheau]

Ð ÐÑÐ, 26.03.2004, Ð 22:43, Tom Lane ÐÐÑÐÑ:
> "Bulatovic Natasa" <[EMAIL PROTECTED]> writes:
> > select id, title from docs where title like 'z%'; or 
> > select id, title from docs where title like 'Z%';
> > It reports the following error:
> > ERROR:  Invalid UNICODE character sequence found (0xc000)
> 
> This is fixed in 7.3.6.

I remember to have stumbled over this bug, too. I poked around in the
code a bit but found nothing that hinted to cause of the bug. So I
wonder what the cause of this bug was?

-- 
Markus Bertheau <[EMAIL PROTECTED]>


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [SQL] Slow sub-selects, max and count(*)

[Greg Stark]

Josh Berkus <[EMAIL PROTECTED]> writes:

> Max() and Count() cannot use indexes for technical reasons.   Browse through 
> the archives of SQL, PERFORM, and HACKERS for about 12,000 discussions on the 
> subject.

Please don't confuse the issue by throwing Max() and Count() into the same
basket.

The issue with Min()/Max() is that the result could be generated efficiently
by scanning indexes but it's just hard, especially given generic aggregate
functions, and the work simply hasn't been done, or even started, yet.

The issue with Count() is that people want the result to be cached in a single
per-table counter, but that can't be done as simply as that because of
transactions. People have discussed complex solutions to this but it's a much
more complex problem than it appears.

They're really two entirely separate issues.

-- 
greg


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings