From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Leon Widdershoven <qaz(at)dds(dot)nl>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Adding a user without expiration date using pgAdmin III causes postgresql Beta1 to crash |
Date: | 2011-05-12 14:31:23 |
Message-ID: | BANLkTim25p8cCts6hhtnreAAajV0jYcuYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, May 5, 2011 at 5:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Leon Widdershoven <qaz(at)dds(dot)nl> writes:
>> I have just installed Postgresql Beta 1 on a new Windows 7 64-bit system
>> (without a previously installed PostgreSQL).
>
>> When using pgAdmin III (included in the installer package) to create a
>> user (Login Role) postgresql crashes.
>
> Hm, this sounds like it's probably the same thing as bug #6005
> http://archives.postgresql.org/pgsql-bugs/2011-05/msg00009.php
>
> which I couldn't reproduce. But both you and that person are using
> Windows, so a Windows-only bug is looking more probable. Could someone
> reproduce this and get a stack trace?
> http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
Based on Tom's recent commits, this might now be fixed in the latest sources.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-05-12 15:24:13 | Re: BUG #6024: pg_dump won't dump ALTERed inherited fields |
Previous Message | Panos Christeas | 2011-05-12 09:14:21 | BUG #6024: pg_dump won't dump ALTERed inherited fields |