Excerpts from Etienne Robillard's message of lun mar 21 12:29:01 -0300 2011:
> $ md5sum postgresql-8.4.7.tar.gz
> 4771d4ae4fd9e7e9b92c22253517508d postgresql-8.4.7.tar.gz
>
> The detached MD5 signature matches the tarball I used for compiling
> postgresql server so I don't think
> its necessary
The following bug has been logged online:
Bug reference: 5939
Logged by: Vincent Chan
Email address: joy717@gmail.com
PostgreSQL version: 9.0
Operating system: Win7 x64
Description:About bytea
Details:
when saving a bytes array,
for example a bytes array which l
I tried with 9.0.3...same problem...
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-5800-corrupted-error-messages-encoding-problem-tp3313951p4248990.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
--
Sent via pgsql-bugs mailing list (pgsql-
The following bug has been logged online:
Bug reference: 5938
Logged by: Craig Sacco
Email address: craig.sa...@gmail.com
PostgreSQL version: 9.0.3
Operating system: Microsoft Windows (all variants, 32 and 64 bit)
Description:PostgreSQL Installer outputs log file with
The following bug has been logged online:
Bug reference: 5940
Logged by: Adriaan
Email address: adriaa...@gmail.com
PostgreSQL version: 8.4 / 9.0
Operating system: Ubuntu
Description:Creating a foreign key on an empty table locks table
Details:
I am using creation o
Thanks,
ALTER ROLE postgres SET time zone 'America/New_York';
Fixed the problem!
I applied this to my dev server DB anyways, so maybe this will be fixed the
next time I migrate to Production.
ALTER DATABASE beta_cms_main SET time zone 'America/New_York';
-Original Message-
From: Robert H
On Tue, Mar 22, 2011 at 5:10 AM, Craig Sacco wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5938
> Logged by: Craig Sacco
> Email address: craig.sa...@gmail.com
> PostgreSQL version: 9.0.3
> Operating system: Microsoft Windows (all variants, 32 and 64
Hi,
The bit of SQL below does not behave the way it should on postgres 8.4.4
(tested by me) and 9.0.3 (verified independently on #postgresql).
The third statement in the quux() function calls the a_bar() function that
should find a single row in the 'bar' table and return its value. This single
On Tue, Mar 22, 2011 at 3:45 PM, Dave Page wrote:
>
>
> On Tue, Mar 22, 2011 at 5:10 AM, Craig Sacco wrote:
>
>>
>> The following bug has been logged online:
>>
>> Bug reference: 5938
>> Logged by: Craig Sacco
>> Email address: craig.sa...@gmail.com
>> PostgreSQL version: 9.0.3
On Tue, Mar 22, 2011 at 4:09 PM, Dave Page wrote:
>
>
> On Tue, Mar 22, 2011 at 3:45 PM, Dave Page wrote:
>>
>>
>> On Tue, Mar 22, 2011 at 5:10 AM, Craig Sacco
>> wrote:
>>>
>>> The following bug has been logged online:
>>>
>>> Bug reference: 5938
>>> Logged by: Craig Sacco
>>> Ema
The following bug has been logged online:
Bug reference: 5941
Logged by: GIMENEZ alex
Email address: parabuenara...@hotmail.com
PostgreSQL version: 8.4
Operating system: windows 7
Description:i don t understand
Details:
hello
i have a probleme to install poker trac
On Tue, 2011-03-22 at 19:39 +, GIMENEZ alex wrote:
>
> i have a probleme to install poker tracker 3
> please help me thank you
This is *not* a bug. Please ask this question to pgsql-general list. You
can subscribe to that list by filling out this form:
http://www.postgresql.org/community/li
On Tue, Mar 22, 2011 at 12:33 PM, Simon Riggs wrote:
>>> This has been fixed for the next releases.
>>
>> For the sake of the archives, it should also be noted that the file is in a
>> secure directory, much as a .pgpass file would be, so this is generally only
>> an issue for the situation descri
All,
At two sites I'm not allowed to share data from (grrr), I've encountered
core dumps of psql. In once case the core dump happens as soon as you
run any query. In the second case, it occurs when you exit.
What both sites have in common is that there's something screwy about
the .psql_histor
On 03/22/11 1:40 PM, Josh Berkus wrote:
All,
At two sites I'm not allowed to share data from (grrr), I've encountered
core dumps of psql. In once case the core dump happens as soon as you
run any query. In the second case, it occurs when you exit.
What both sites have in common is that there
2011/3/22 Devrim GÜNDÜZ :
> On Tue, 2011-03-22 at 19:39 +, GIMENEZ alex wrote:
>>
>> i have a probleme to install poker tracker 3
>> please help me thank you
>
> This is *not* a bug. Please ask this question to pgsql-general list. You
> can subscribe to that list by filling out this form:
>
> h
On 22/03/11 10:51 AM, Alvaro Herrera wrote:
> Excerpts from Etienne Robillard's message of lun mar 21 12:29:01 -0300 2011:
>
>
>> $ md5sum postgresql-8.4.7.tar.gz
>> 4771d4ae4fd9e7e9b92c22253517508d postgresql-8.4.7.tar.gz
>>
>> The detached MD5 signature matches the tarball I used for compilin
Etienne Robillard writes:
> I also just noticed the compiler was set to llvm-gcc and not gcc4. I
> will try again with gcc 4.4.5.
I'd bet on that being the issue. How recent is your copy of llvm?
We know that llvm produced bad code for PG up till not too long ago
(maybe a year, I'm not sure).
On 22/03/11 06:26 PM, Tom Lane wrote:
>
> I'd bet on that being the issue. How recent is your copy of llvm?
> We know that llvm produced bad code for PG up till not too long ago
> (maybe a year, I'm not sure).
>
> regards, tom lane
>
$ llvm-gcc --version
llvm-gcc (GCC) 4.2
Hi,
I was wondering if this was considered a bug, and if so what were the plans to
fix it: http://archives.postgresql.org/pgsql-bugs/2005-08/msg00211.php
I searched the: pgsql-bug archive and found nothing
I also searched the wiki to do list and found nothing
But I could have missed it.
Sincerel
> Hi,
> I was wondering if this was considered a bug, and if so what were the plans
> to fix it: http://archives.postgresql.org/pgsql-bugs/2005-08/msg00211.php
>
> I searched the: pgsql-bug archive and found nothing
> I also searched the wiki to do list and found nothing
> But I could have missed
On Wed, Mar 23, 2011 at 08:05, Kasia Tuszynska wrote:
> I was wondering if this was considered a bug, and if so what were the plans
> to fix it: http://archives.postgresql.org/pgsql-bugs/2005-08/msg00211.php
The wave dash issue is not postgres-specific; some other converter just
replace it with '
On Wed, Mar 23, 2011 at 10:58, Tatsuo Ishii wrote:
> So if we want to do a round trip conversion between
> EUC-JP and UTF-8, we have to choose either U+FF5E OR U+301C. We have
> chosen U+FF5E. If we change the mapping, many existing applications
> would break.
I heard a request a few times for an
21.03.2011 15:51, Susanne Ebrecht пишет:
Hello Yora Sokolov,
Maybe this is not a bug - just an inconsistence:
Look here (tested with 9.0):
=# set timezone='+3.5';
SET
=# select current_timestamp;
now
--
2011-03-21 16:05:34.761112+03:30
(1 row)
I
>> So if we want to do a round trip conversion between
>> EUC-JP and UTF-8, we have to choose either U+FF5E OR U+301C. We have
>> chosen U+FF5E. If we change the mapping, many existing applications
>> would break.
>
> I heard a request a few times for an additional one-directional conversion
> fro
On Wed, Mar 23, 2011 at 13:02, Tatsuo Ishii wrote:
> I think what we can do best here is, adding new encoding and default
> conversion.
Agreed if the encoding is added as an user-defined encoding.
I don't want to add built-in encodings only for Japanese language any more.
--
Itagaki Takahiro
-
> Agreed if the encoding is added as an user-defined encoding.
> I don't want to add built-in encodings only for Japanese language any more.
I do not agree here. Adding one more encoding/conversion is not big
deal.
Anyway these soltions would come to be real after one or two releases
at the earli
27 matches
Mail list logo
