Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> But it hasn't got done yet. (Peter, would it be
>> easy to make GUC handle this? There'd need to be some way to cause
>> guc.c to do a putenv() ...)
> I thought pg_control was the place for this. Any idea how long a locale
> string can legally be
Patrik Kudo <[EMAIL PROTECTED]> writes:
> select * from elever where userid like 'walth%'; <-- Not OK!
> Droping and recreating the index solves the problem, but that's not
> good enough for me since the problem has reoccured on a different
> machine with a different database. vacuum and vacuum a
Stephen,
> How come nobody's ever thought of cursors?
>
> DECLARE foo CURSOR FOR SELECT stuff FROM stuff WHERE foo ORDER BY
> something;
>
> Hop forward N rows?
> MOVE FORWARD $n IN foo
>
> Want M rows?
> FETCH FORWARD $m IN foo
I'm intrigued by this. How would I ret
Paul,
I'm afraid that much of that was over my head. In fact, I'm keeping it
as an example in case I ever need to do something similar. Forward your
info and I'll include credit in the source :-)
In general terms, I've always depended on the PHP to select a "page" of
results, u
Hi!
We're using postgres 6.5.3 for an application where we, among other
things, store information about users. On two separate occations on
two different servers we've experienced problems with indices on the
same table (out of over 100).
The problem is that postgres refuse to find a certain row
