DragonFly users List (threaded) for 2010-06
Re: DragonFly 64-bit stability
What version of postgres are you running? I am able to load 8.4 on an
DragonFly tyler-bsd.local 2.7-DEVELOPMENT DragonFly
v18.104.22.168.g6846f-DEVELOPMENT #4: Thu Jun 10 02:46:08 CDT 2010
On Fri, Jun 11, 2010 at 1:36 AM, Francois Tigeot <email@example.com> wrote:
> On Thu, Jun 10, 2010 at 06:55:53PM -0600, Samuel J. Greear wrote:
>> On Thu, Jun 10, 2010 at 6:47 PM, Justin C. Sherrill
>> <firstname.lastname@example.org> wrote:
>> > On Thu, June 10, 2010 4:32 pm, Francois Tigeot wrote:
>> >> Installing applications from pkgsrc went well.
>> >> Unfortunately, running Postgres is a different matter:
>> >> # /usr/pkg/etc/rc.d/pgsql start
>> >> Starting pgsql.
>> >> seg-fault accessing address 0x580000 rip=0x80077037d pid=20186
>> >> p_comm=pg_ctl Segmentation fault
>> > Is this from a prebuilt binary or one that you compiled yourself? It may
>> > be worth building locally if you did not before.
> It was built locally.
>> > Otherwise: http://www.postgresql.org/support/submitbug
>> If I had to guess I would say it is likely that this is our bug,
>> probably in one of the kernel sysv subsystems.
> Yeah, I don't believe Postgres is to blame either.
> During the pkgsrc build, many make instances were also dying with signal 11.
> Every time I have tested the amd64/x86-64 DragonFly port, I found out this
> segfault problem was a constant.
> Francois Tigeot