pg.ddx.io pgsql-hackers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Peter Eisentraut <peter_e@gmx.net>
To: Gregory Stark <stark@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org, Greg Stark <greg.stark@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>
Subject: Re: [SPAM] Re: posix_fadvise v22
Date: Mon, 05 Jan 2009 10:42:52 +0200
Message-ID: <4961C80C.6030307@gmx.net> (raw)
In-Reply-To: <87iqowt3ba.fsf@oxford.xeocode.com>
References: <FDDBA24E-FF4D-4654-BA75-692B3BA71B97@enterprisedb.com>
<603c8f070901012011hca2c36flf527a5cd01695205@mail.gmail.com>
<262184F8-1206-4E2C-B50F-9FF84E63C1B6@enterprisedb.com>
<200901032342.19435.peter_e@gmx.net>
<87iqowt3ba.fsf@oxford.xeocode.com>
Gregory Stark wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
>
>> On Friday 02 January 2009 06:49:57 Greg Stark wrote:
>>> The guc run-time check is checking for known-buggy versions of glibc
>>> using sysconf to check what version of glibc you have.
>> Could you please mention the bug number in the relevant source code comments?
>
> It's Debian bug# 312406 which was fixed in Debian release 2.3.5-3. So it's
> probably one of these but searching for posix_fadvise doesn't find anything in
> their bug tracker:
The way I read this is that this was a temporary kernel/libc mismatch in
a development version of Debian 3 years ago that was fixed within 2
months of being reported and was never released to the general public.
So it would be on the same level as any of a million temporary breakages
in Linux distributions under development.
Unless there are other reports of this problem, I wouldn't bother
testing or working around this at all. If people are running PostgreSQL
8.4+ on Debian unstable June 2005 with kernel 2.4, they cannot be helped.
view thread (41+ messages) latest in thread
Message-ID: <4961C80C.6030307@gmx.net> Permalink: ../4961C80C.6030307@gmx.net/ Also on: postgresql.org/message-id/4961C80C.6030307@gmx.net ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-hackers@postgresql.org Cc: peter_e@gmx.net, stark@enterprisedb.com, greg.stark@enterprisedb.com, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, itagaki.takahiro@oss.ntt.co.jp Subject: Re: [SPAM] Re: posix_fadvise v22 In-Reply-To: <4961C80C.6030307@gmx.net> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox