If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]
To report any other bug, fill out the form below and e-mail it to
[EMAIL PROTECTED]
If you not only found the proble
This problem is so simple, the subject pretty much says it all. For
the sake of completeness, I'm running PostgreSQL 7.2.1 as supplied by
RedHat in their 7.3 release for i386. This bug report pertains only
to the psql front end.
The command
\d
all by itself (with no arguments) lists all rela
Hi Tatsue Ishii,
Ok, but problem is, when i try encode with unicode, it also reject
me invalid UNICODE charater :-(
I already try few client, like borland's SQL explorer, zde... and
restore program come with postgresql...
Sorry, i would like to a special request. After i read preious mes
Tatsuo Ishii wrote:
Ok, but problem is, when i try encode with unicode, it also reject
me invalid UNICODE charater :-(
Show me the entire error message please.
Ok... error like this...
ERROR : Invalid UNICODE character sequence found (0xe5a672)...
the input charat
Anand <[EMAIL PROTECTED]> writes:
> When I run the select statement given below, the postgres server dies on
> a SIGSEGV. This is quite annoying.
Hmm ... works for me.
You should check that the plpgsql.so mentioned by the CREATE FUNCTION
call is the same version of Postgres as your backend. Wei
Webb Sprague wrote:
>
> I am getting a "field is too small" error in an Access
> DB running over ODBC. The field in question is
> varchar(32).
>
> Here is the weird thing: I am inserting into a table
> with a rule that sends the result to a different
> table.
Are you using a DO INSTEAD rule ?
