Danny Kao ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Encoding problem
Long Description
I have tried "initdb --encoding=BIG5"
then doing some create table and insert.
As shows below,it seems loss one byte "\",
and dumping
Quoting [EMAIL PROTECTED]:
> Hi,
>
> We just find out a small bug with the getBigDecimal(int i) method in
> ResultSet (postgresql 7.1 beta6)
>
> Th symptom is :
>
> We cannot read a decimal value with getBigDecimal() although, we can set
> it
>
> We solve the problem temporary by replacing th
> Danny Kao ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> Encoding problem
>
> Long Description
> I have tried "initdb --encoding=BIG5"
You cannot do that (documented in README.mb). If you want to use
traditional ch
Corrected. Thanks.
[EMAIL PROTECTED] writes:
> Philip ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> Doc bug: libpq PQconnectPoll()
>
> Long Description
> In the online docs:
>
> http://www.postgresql.org/users-lounge
Hello,
On Sun, 25 Feb 2001, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > postmaster crashes every time a user tries to access database from psql
>
> Does it fail for all users, or just some?
For one user. I deleted user and this database and created them again. Now
it works.
> Did it used
We are running a PostgreSQL server on a Debian 2.2 and we have problems with
the
mothod getTimestamp() of the ResultSet class;
we have find that if we insert a timestamp on a table, for example
'2000-10-09 12:21:34.321+01'
when we try to read that tuples using the JDBC driver we have an exception
Dear postgresql developers,
I have found a small annoying bug in the SQL
parser,
executing the following query;
select * from table where field ~*
'*';
or
select * from table where field ~*
'+';
generate the following error:
regcomp failed with error repetition-operator operand
POSTGRESQL BUG REPORT TEMPLATE
Your name : Thomas Waelde
Your email address : [EMAIL PROTECT
Dear Sir :
Thanx. After tried it again, it still couldn't work now.
The result is the same error.
*
template1=# \encoding
EUC_TW
template1=# \z
Access permissions for database "template1"
Relation | Access permissions
--+---
Dear Lamar and Tom
I have unset LANG (blank), wiped the old database, and start postmaster
(init.d). The result of the regression test looks pretty fine, no failure.
What's about other application when LANG=blank?
Thank you very much for your support.
Regards Martin
Lamar Owen wrote:
> On
Dear Reinhard
I have unset LANG (blank), wiped the old database, and start postmaster
(init.d).
The result of the regression test looks pretty fine, no failure.
Thank you very much for your support.
Regards Martin
Reinhard Max wrote:
> On Mon, 19 Mar 2001 [EMAIL PROTECTED] wrote:
>
> > Insta
On Wed, 21 Mar 2001, Romolo Manfredini wrote:
> Dear postgresql developers,
> I have found a small annoying bug in the SQL parser,
>
> executing the following query;
>
> select * from table where field ~* '*';
>
> or
>
> select * from table where field ~* '+';
>
> generate the following er
> Dear Sir :
> Thanx. After tried it again, it still couldn't work now.
> The result is the same error.
> *
> template1=# \encoding
> EUC_TW
> template1=# insert into a values('許\多');
> INSERT 18762 1
What is \261\\? It does not seem to
Test case:
create table test (data text unique);
Outside of psql, run this command (This is for bash):
while true ; do echo "begin work; insert into test (data) values ('This
is a test string.'); commit work;" ; done | psql
Watch the resident set size of the postmaster that the psql is connect
14 matches
Mail list logo
