Re: Adding a user without expiration date using pgAdmin III causes postgresql Beta1 to crash - Mailing list pgsql-bugs

From Robert Haas
Subject Re: Adding a user without expiration date using pgAdmin III causes postgresql Beta1 to crash
Date
Msg-id BANLkTim25p8cCts6hhtnreAAajV0jYcuYg@mail.gmail.com
Whole thread Raw
In response to Re: Adding a user without expiration date using pgAdmin III causes postgresql Beta1 to crash  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, May 5, 2011 at 5:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Leon Widdershoven <qaz@dds.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. =A0But both you and that person are using
> Windows, so a Windows-only bug is looking more probable. =A0Could someone
> reproduce this and get a stack trace?
> http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_Postgr=
eSQL_backend_on_Windows

Based on Tom's recent commits, this might now be fixed in the latest source=
s.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: "Panos Christeas"
Date:
Subject: BUG #6024: pg_dump won't dump ALTERed inherited fields
Next
From: Tom Lane
Date:
Subject: Re: BUG #6024: pg_dump won't dump ALTERed inherited fields