"Andras Got" <[EMAIL PROTECTED]> writes:
> I'm trying to select with LOWER/UPPER and INITCAP but they return bad values
> after hungarian accentuated letters (e.g: é á ű
> ú Šó ü).
Are you sure you are using the right locale and database encoding?
If so, what are they?
There are some loca
"Shawn Dong" <[EMAIL PROTECTED]> writes:
> I install a completely new Fedora Core 4, and did not choose to install the
> PostgresSQL while installing the Fedora.
If you want a canned solution, why aren't you installing the RPM (either
Red Hat's version or the PGDG one)?
You're welcome to figure o
"Dave Byrne" <[EMAIL PROTECTED]> writes:
> Every vacuum full analyze errors out with:
> ERROR: buffer x is not owned by resource owner TopTransaction
> Pls contact if any additional info is needed.
It works fine for everyone else, so yeah, some more info is needed.
What have you done different
Giles Morant wrote:
> I agree we cannot just throw the semi-colon away, but the action of
> "\d" to assume the semi-colon is an argument and thus invalid is in my
> view wrong.
I didn't say what we are doing is right, I said fixing it would not be
worth it. If you want, submit a patch and we can
This is not the place to report odbc problems. The odbc project has its
own mailing lists.
---
Farid Z wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2190
> Logged by: Farid Z
> Emai
This is not the place to report jdbc problems. The jdbc project has its
own mailing lists.
---
Kris Senden wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2189
> Logged by: Kris Sende
The following bug has been logged online:
Bug reference: 2189
Logged by: Kris Senden
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.2
Operating system: Windows XP/2K/2003
Description:Prepared Statement is not parsed correctly
Details:
Recently we discovere
The following bug has been logged online:
Bug reference: 2190
Logged by: Farid Z
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows 2000
Description:ODBC SQLPrimaryKeys PK_NAME missing info
Details:
No info is returned for PK_NAME in
I agree we cannot just throw the semi-colon away, but the action of
"\d" to assume the semi-colon is an argument and thus invalid is in my
view wrong.
On 1/19/06, Bruce Momjian wrote:
>
> We can't just throw away semicolons, e.g.:
>
> \test=> \f ;
> Field separator is ";".
>
> The
The following bug has been logged online:
Bug reference: 2191
Logged by: Farid Z
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows 2000
Description:ODBC SQLForeignKeys Resultset missing info
Details:
ODBC SQLForeignKeys resultset has
The following bug has been logged online:
Bug reference: 2194
Logged by: Shawn Dong
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Fedora Core 4
Description:Start Script in the package doesn't work
Details:
I install a completely new Fe
The following bug has been logged online:
Bug reference: 2192
Logged by: John Jorgensen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: IRIX 6.5.22f
Description:misbehaving IRIX strtod() subverts parsing of "infinity"
Details:
When I ran
Seneca Cunningham wrote:
Steven Mooij wrote:
Some additional info. We repeated the test on different hardware with
unfortunately the same result. This is the output of the postgresql
logfile of that experiment:
[log messages about processes kill 9ed]
This time we tested with post
Hello folks,
my system is a SuSE 10.0 Linux and a plain PostgreSQL 8.1.2 (compiled by
myself, NLS enabled). LOCALE is set to de_DE.UTF-8.
The bug shows up using the operator '~*' with umlauts. An easy way to produce
a faulty result is
select 'XXXMÜLLERYyyy' ~* '.*müller.*';
The result should
The following bug has been logged online:
Bug reference: 2193
Logged by: Andras Got
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.4, 8.1.1
Operating system: FreeBSD and Linux
Description:INITCAP and LOWER/UPPER string conversion error
Details:
Hi,
8.0.4
The following bug has been logged online:
Bug reference: 2188
Logged by: venkat
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Windows Xp Professional Service Pack 2
Description:win32 version of 8.1.2 is not getting installed
Details:
D
The following bug has been logged online:
Bug reference: 2187
Logged by: Dave Byrne
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: win32
Description:ERROR: buffer x is not owed by resource owner
TopTransaction
Details:
Every vacuum
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> in my machine (win xp) i was trying to start psql (8.1.1) with
> log_min_messages to debug5 (just to see the messages :) but even the
> service start i cannot use psql nor pgadmin i receive an error of
> server closed the connection unexpectedly
Can'
The following bug has been logged online:
Bug reference: 2195
Logged by: Jaime Casanova
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: Windows XP
Description:log_min_messages crash server when in DEBUG3 to 5
Details:
Hi,
in my machine
On 1/17/06, Francisco Leovey <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2176
> Logged by: Francisco Leovey
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.2
> Operating system: Linux
> Description:Pgadmin III
Giles Morant wrote:
> I agree we cannot just throw the semi-colon away, but the action of
> "\d" to assume the semi-colon is an argument and thus invalid is in my
> view wrong.
True, but to fix it would require we know which backslash commands can
throw it away, and which cannot, and it doesn't se
21 matches
Mail list logo
