> By Chinese here, I mean BIG5 encoding character which is a widely used
> encoding in HK and Taiwan.
Ok. PostgreSQL does support BIG5 in the *frontend* side.
> I've done a new check on it, I found JDBC and ODBC driver still report
> the error message but psql do not (may be as you said, I've do
I am not sure how to do that. \? is already pretty full on the screen.
Ideas?
---
[EMAIL PROTECTED] wrote:
> Harald Armin Massa ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more sever
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I would love to know why doing this TODO item is so hard. Every time I
> ask Jan, he says it is very hard and it never gets done.
It doesn't look that hard to me, but I haven't tried yet ...
regards, tom lane
-
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I assume this completes the TODO item:
> > o Fix PL/PgSQL to handle quoted mixed-case identifiers
>
> It would if it worked, but it doesn't --- for one thing, it seems
> to allow empty identifiers (surely {DQUOTE}* should be
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I assume this completes the TODO item:
> o Fix PL/PgSQL to handle quoted mixed-case identifiers
It would if it worked, but it doesn't --- for one thing, it seems
to allow empty identifiers (surely {DQUOTE}* should be {DQUOTE}+).
I'm not convince
[EMAIL PROTECTED] writes:
> create aggregate aggint4sum (basetype = int4, sfunc = int4_sum, stype = int4);
This doesn't work because there's no int4_sum(int4, int4).
regression=# \df int4_sum
List of functions
Result data type | Name | Argument data types
--
The pg_ctl code has this warning:
# FIXME: This is horribly misconceived.
# 1) If password authentication is set up, the connection will fail.
# 2) If a virtual host is set up, the connection may fail.
# 3) If network traffic filters are set up tight enou
I assume this completes the TODO item:
o Fix PL/PgSQL to handle quoted mixed-case identifiers
It is quite a bit of lex code, but I assume it was required. No one
else was able to fix this item.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://can
Dan Graham ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Problmes creating aggregate functions in 7.2.1
Long Description
I've included a short sample which shows what I'm having problems with.
I using version 7.2.1 on Slack
>> Two bugs has been found in the SQL parser and Multibyte char support:
>>
>What is the encoding for "chinese char"? You need to give us more info.
By Chinese here, I mean BIG5 encoding character which is a widely used
encoding in HK and Taiwan. My setup:
Db encoding: EUC_TW
C
>> Two bugs has been found in the SQL parser and Multibyte char support:
>>
>What is the encoding for "chinese char"? You need to give us more
>info.
By Chinese here, I mean BIG5 encoding character which is a widely used
encoding in HK and Taiwan.
My setup:
Db encoding: EUC_TW
[EMAIL PROTECTED] writes:
> I would like to know what this message means, maybe a bug??
> ERROR: XLogFlush: request 0/6173A2D8 is not satisfied --- flushed only to 0/616E519C
This suggests a corrupted LSN on some disk page, but without any context
I can't say more than that.
> This message is
Jose Soares ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
XlogFlush
Long Description
Hi all,
I would like to know what this message means, maybe a bug??
psql> select * from capi;
ERROR: XLogFlush: request 0/6173A2D8 is no
13 matches
Mail list logo
