On Sat, 2002-12-14 at 15:33, [EMAIL PROTECTED] wrote:
> PostgreSQL 7.2 will allways do a full table scan when the index field
> is a bigint. even with a "where bigkey = 99" clause.
This is a known problem: you need to enclose the integer literal in
single quotes, or cast it to int8 for the optimiz
L.S.
It seems that '\encoding' only shows the correct client encoding if any
changes are applied by using '\encoding' itself.
If the client encoding is changed by using 'set names' or 'set
client_encoding', the result of '\encoding' will still be the old one used.
However, the encoding seems t
