Fwd: [HACKERS] Fwd: Debug strategy for musl Postgres?

From: John Mudd <johnbmudd(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Fwd: [HACKERS] Fwd: Debug strategy for musl Postgres?
Date: 2014-04-13 21:00:32
Message-ID: CAGDMk9EgLqjgGypfSoDtkbNAHmVc_x7p8kx9PHh1jKa5YQXhcg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Sun, Apr 13, 2014 at 4:28 PM, Andres Freund <andres(at)2ndquadrant(dot)com>wrote:

> Hi,
>
> On 2014-04-13 16:08:00 -0400, John Mudd wrote:
> > I built Postgres 9.3.4 from source on top of the musl C library,
> > http://www.musl-libc.org/
> > I also built zlib, bzip2, ncurses, openssl, readline and Python using
> musl
> > as a foundation for Postgres.
> >
> > I'm using musl to increase the portability of the Postgres binary. I
> build
> > on Ubuntu 13.10 but will runs on older Linux boxes.
> >
> > So far I get better results with the musl Postgres built on modern Ubuntu
> > and running on an old kernel than building Postgres directly on the old
> > Linux using standard C library. But the musl Postgres is still not
> working
> > fully. I'm not getting responses from the server.
>
> I tend to think that this is more a matter for the musl devs than
> postgres. Postgres works on a fair numbers of libcs and musl is pretty
> new and rough around the edges.
>

Okay. I just wanted to check here too.

>
> > clock_gettime(0, 0xbfffa5a8) = -1 ENOSYS (Function not
> implemented)
>
> This looks suspicious.
>
> > gettimeofday(NULL, {300, 0}) = 0
> > poll([{fd=3, events=POLLOUT|POLLERR, revents=POLLOUT}], 1, 3000) = 1
> > sendto(3, "\0\0\0?\0\3\0\0user\0jmudd\0database\0jmud"..., 63, 0x4000,
> > NULL, 0) = 63
> >
> > clock_gettime(0, 0xbfffa5a8) = -1 ENOSYS (Function not
> > implemented)
> > gettimeofday(NULL, {300, 0}) = 0
> > poll([{fd=3, events=POLLIN|POLLERR}], 1, 3000) = 0
>
> Here a poll didn't return anything. You'll likely have to look at
> the server side.
>

Yes, the server. It's in a tight loop. This is all it's doing. Thanks, I'll
look into this.

clock_gettime(0, 0xbfffded8) = -1 ENOSYS (Function not
implemented)
gettimeofday(NULL, {300, 0}) = 0
clock_gettime(0, 0xbfffded8) = -1 ENOSYS (Function not
implemented)
gettimeofday(NULL, {300, 0}) = 0
clock_gettime(0, 0xbfffded8) = -1 ENOSYS (Function not
implemented)
gettimeofday(NULL, {300, 0}) = 0
clock_gettime(0, 0xbfffded8) = -1 ENOSYS (Function not
implemented)
gettimeofday(NULL, {300, 0}) = 0
clock_gettime(0, 0xbfffded8) = -1 ENOSYS (Function not
implemented)
gettimeofday(NULL, {300, 0}) = 0

>
> Greetings,
>
> Andres Freund
>
> --
> Andres Freund http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message digoal 2014-04-14 01:44:42 BUG #10013: PostgreSQL 9.4 initdb FATAL: could not write to file "pg_xlog/xlogtemp.3590": No space left on devi
Previous Message Andres Freund 2014-04-13 20:28:55 Re: Fwd: Debug strategy for musl Postgres?

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2014-04-13 21:46:20 Re: Problem with txid_snapshot_in/out() functionality
Previous Message Heikki Linnakangas 2014-04-13 20:39:29 Race condition between PREPARE TRANSACTION and COMMIT PREPARED (was Re: Problem with txid_snapshot_in/out() functionality)