"Dmitry Ryabov" writes:
> In the version 9.1 I was surprised to find that the function "upper" now is
> not working as before. For example:
> select upper ('SISTEM AYGıTLARı') = 'SISTEM AYGITLARI'
> in postgresql 9.0 returns true, but in postgresql 9.1 - false.
It sounds like you didn't use t
The following bug has been logged online:
Bug reference: 6230
Logged by: Dmitry Ryabov
Email address: dmitry-rya...@mail.ru
PostgreSQL version: 9.1
Operating system: Windows x64
Description:strange changes in behavior of string functions
Details:
In the version 9.1
On Wed, Sep 28, 2011 at 11:05, Tom Lane wrote:
> "Itagaki Takahiro" writes:
>> Our documentation says OIDS and HEADER options in COPY command take [
>> boolean ] arguments, but actually they don't accept any arguments. We can
>> only set them to TRUE by specifying their names.
>
> Um, these examp
"Itagaki Takahiro" writes:
> Our documentation says OIDS and HEADER options in COPY command take [
> boolean ] arguments, but actually they don't accept any arguments. We can
> only set them to TRUE by specifying their names.
Um, these examples all work fine for me in HEAD:
regression=# copy ten
Alvaro Herrera writes:
> Excerpts from Max Kunz's message of mar sep 27 13:50:57 -0300 2011:
>> i have detected a problem after postgres logs "statistics buffer is full":
>> The database achieves farther on connections from the clients but no one
>> could process a statement and neither of the con
Excerpts from Max Kunz's message of mar sep 27 13:50:57 -0300 2011:
>
> The following bug has been logged online:
>
> Bug reference: 6229
> Logged by: Max Kunz
> Email address: ad...@m4ximus.de
> PostgreSQL version: 8.1.3
> Operating system: Suse
> Description:Postgr
The following bug has been logged online:
Bug reference: 6229
Logged by: Max Kunz
Email address: ad...@m4ximus.de
PostgreSQL version: 8.1.3
Operating system: Suse
Description:Postgresql crashes after: LOG: statistics buffer is full
Details:
Hello,
i have detected a
On Tue, Sep 27, 2011 at 5:06 AM, wrote:
> Hello,
>
> I've encountered some problems with the updated ENUM in PosgreSQL 9.1:
>
> 1. We can use ALTER TYPE to add enum values, but there is no matching command
> to remove values, which makes this an incomplete solution.
you can manually delete from
The following bug has been logged online:
Bug reference: 6228
Logged by: Craig
Email address: lumberjackches...@gmail.com
PostgreSQL version: 8.2
Operating system: Windows Server 2008 R2
Description:Failed to set permissions on the installed files
Details:
Hi,
I ha
wrote:
> I've encountered some problems with the updated ENUM in PosgreSQL
> 9.1:
No matter how I tilt my head, I can't see any of those issues as
bugs. You have two feature requests and a question about how to
work around problems you're having with direct modifications to the
system tables.
Excerpts from pratikchirania's message of mar sep 27 08:22:45 -0300 2011:
> Hi,
>
> Thanks for the replies and confirmation.
> Can you provide me with any defect number or some equivalent for tracking
> purpose?
Hmm, this was fixed in the master Git branch (what's going to become 9.2
eventually)
Hi,
Thanks for the replies and confirmation.
Can you provide me with any defect number or some equivalent for tracking
purpose?
Regards, Pratik
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Timezone-issues-with-Postgres-tp4809498p4844991.html
Sent from the PostgreSQL
Hello,
I've encountered some problems with the updated ENUM in PosgreSQL 9.1:
1. We can use ALTER TYPE to add enum values, but there is no matching command
to remove values, which makes this an incomplete solution.
2. "ALTER TYPE ... ADD cannot be executed from a function or multi-command
stri
13 matches
Mail list logo
