>
>No,
>actually I haven't yet.
>I have noticed that during the time
the query
>executes there is neither so much CPU load nor network
(communication
>with db) load. The client seems to hang, then after a
minute or so the
>query returns data.
>I also thought this problem
could be related to
Hi all,
I recently came accross a problem with the use of IN clause in a
partial index with a varchar(3) field. Int, char and text seems to be
OK (test case is provided below).
Version is 8.2.3 running on a Fedora Core 3 (RPM rebuilt from the PGDG ones).
test=# SELECT version();
Did you run 'nmake /f bcc32.mak' from src/ before going to
src/interfaces/libpq?
---
CN Liou wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3182
> Logged by: CN Liou
> Email address:
"Guillaume Smet" <[EMAIL PROTECTED]> writes:
> test=# CREATE TABLE test_in (field varchar(3));
> CREATE TABLE
> test=# CREATE INDEX idx_test_in ON test_in(field) WHERE field IN('1', '2');
> ERROR: functions in index predicate must be marked IMMUTABLE
Hmm. This is generating a coercion from varch
FYI, 8.3 will have an 'isodow' that conforms to ISO week start:
test=> select current_date-2, date_part('dow', current_date-2),
test->date_part('isodow', current_date-2);
?column? | date_part | date_part
+---+---
200
Zubkovsky, Sergey wrote:
> Hello.
>
>
>
> In spite of the fact that as it was outlined in the "change log" to
> PostgreSQL 8.2.2, the bug of the periodical "permission denied" error
> occurrence was fixed:
>
>
>
> “Fix bogus "permission denied" failures occurring on Windows due to
> attem
I have noticed the same BUG in 8.2.3:
The ~* operation did not match cyrillic upper and lower case letters in
utf-8 encoding.
Still the Helmar's fix solves the problem (see
http://archives.postgresql.org/pgsql-bugs/2006-01/msg00200.php ).
Is there (or is it planned) an "official" solution?
Magnus Hagander wrote:
>
> The obvious question before we even think about anything else - any
> antivirus, antispyware or any other third party software on the machine
> that may be using a filter driver?
Any idea how easy would it be to log the installed filter drivers at
startup? If we can gat
