hi,
If you create a table with one of the columns defined as int8, then the
index created on this column does not work. When I use explain to see
the plan, it is always seq scan instead of index scan as one would expect.
Other types of columns work fine (int4, string ...).
Hao
===
Hi
I want to use tcl to access postgres sql databases.
I ran ./configure
(See attached file: config.status)
/usr/local/bin/make gave me that error
(See attached file: temp)
Can you help me
Thank you
Jacques Talbot
config.status
Description: Binary data
temp
Description: Binary data
> > So, it is still a mystery for me
> You probably need the locale for sorting the single character letters
> but you don't want the collation values of the multiple character ones.
> I think you're probably going to need to get an alternate locale
> file but I'm not sure what's involved in t
Note: forwarded message attached.
__
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
--- Begin Message ---
Dear Sir
While inserting long string in Database table I am
getting following error message.
esev=> \
I'm not sure this is true. As far as the system is concerned this is
the correct ordering. ;) If you don't want collation based on your locale
I'd suggest either turning off locale in postgres (see configure
options) or initdb in "C" locale, you don't need to change the system's
collation to do t
On Thu, 6 Dec 2001, Hao He wrote:
> hi,
>
> If you create a table with one of the columns defined as int8, then the
> index created on this column does not work. When I use explain to see
> the plan, it is always seq scan instead of index scan as one would expect.
> Other types of columns work f
Anthony Chavez ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
libpq: Operations following PQfinish() work.
Long Description
The PGconn *conn argument to PQfinish() is not set to NULL. As a result, calling
libpq functions---i
