Hello,
A have written a program that randomly crashes on Solaris 10. This
program has been tested with valgrind without any error and runs fine on
all other systems I have. I cannot reproduce this bug with a minimal
program.
Backtrace :
Core was generated by `/usr/local/bin/rpl -csd
BERTRAND Joel writes:
> A have written a program that randomly crashes on Solaris 10. This
> program has been tested with valgrind without any error and runs fine on
> all other systems I have. I cannot reproduce this bug with a minimal
> program.
Given that the crash is way down inside
The following bug has been logged online:
Bug reference: 5660
Logged by: Mikio
Email address: tkbysh2...@yahoo.co.jp
PostgreSQL version: 9.0 RC1
Operating system: Windows XP SP3 Japanese
Description:Can't start db service if specify
effective_io_concurrency
Details:
The following bug has been logged online:
Bug reference: 5661
Logged by: Mikio
Email address: tkbysh2...@yahoo.co.jp
PostgreSQL version: 9.0 RC1
Operating system: Windows XP SP3 Japanese
Description:The character encoding in logfile is confusing.
Details:
I'm using
On Thu, Sep 16, 2010 at 7:52 PM, Mikio wrote:
> Operating system: Windows XP SP3 Japanese
> I'm using postgresql 9.0 rc1, and I specified 10 for
> effective_io_concurrency in postgresql.conf.
> I restarted postgresql windows service, but the service didn't start.
Unfortunately, effective_io_con
"Mikio" writes:
> I'm using postgresql 9.0 rc1, and I specified 10 for
> effective_io_concurrency in postgresql.conf.
> I restarted postgresql windows service, but the service didn't start.
This is unsurprising: you can only set effective_io_concurrency on
platforms that have posix_fadvise(), whi
On Thu, Sep 9, 2010 at 12:22 PM, Mark Llewellyn wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5650
> Logged by: Mark Llewellyn
> Email address: mark_llewel...@adp.com
> PostgreSQL version: 9.0 RC1
> Operating system: Windows XP
> Description: P
On Wed, Sep 8, 2010 at 11:42 AM, Tom Lane wrote:
> Valentine Gogichashvili writes:
>> CREATE TYPE ta AS (a1 integer, a2 text);
>> CREATE TYPE tb AS (b1 integer, b2 ta);
>
>> DECLARE
>> a ta;
>> b tb;
>> BEGIN
>
>> SELECT 1, 'a' INTO a; -- ok
>
>> SELECT ROW(10, 'a') INTO b.b2; -- ok in 8
On Fri, Sep 10, 2010 at 9:31 AM, Euler Taveira de Oliveira
wrote:
> Mladen Gogala escreveu:
>> Optimizer chooses to scan each partitioned table sequentially, instead of
>> using the available index:
>>
> This is not a bug. How would the optimizer know that the maximum value is in
> that specific p
Robert Haas writes:
> On Wed, Sep 8, 2010 at 11:42 AM, Tom Lane wrote:
>>> SELECT ROW(10, 'a') INTO b.b2; -- ok in 8.4 but fails in 9.0 [ERROR:
>>> invalid input syntax for integer: "(10,a)"]
>>> SELECT 100, 'a' INTO b.b2; -- ok in 9.0 but fails in 8.4 [ERROR: cannot
>>> assign non-compos
On Thu, Sep 16, 2010 at 9:30 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Wed, Sep 8, 2010 at 11:42 AM, Tom Lane wrote:
SELECT ROW(10, 'a') INTO b.b2; -- ok in 8.4 but fails in 9.0 [ERROR:
invalid input syntax for integer: "(10,a)"]
>
SELECT 100, 'a' INTO b.b2; -- ok in 9.
On 09/16/2010 07:12 PM, Mikio wrote:
The following bug has been logged online:
Bug reference: 5661
Logged by: Mikio
Email address: tkbysh2...@yahoo.co.jp
PostgreSQL version: 9.0 RC1
Operating system: Windows XP SP3 Japanese
Description:The character encoding in logf
Hi Mark,
On of my college (Sujeet) has found a way to reproduce the same behaviour.
1. Installed PG 9.0 on Win XP SP3
2. Stop the Postgresql-9.0 service from service manager console
3. Create pgpass.conf in postgres (service account) user's profile with an
incorrect password deliberately.
(Refer:
13 matches
Mail list logo
