Re: [HACKERS] For review: Server instrumentation patch

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Subject: Re: [HACKERS] For review: Server instrumentation patch
Date: 2005-08-14 16:26:02
Message-ID: 42FF709A.1050601@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Andreas Pflug wrote:

> Tom Lane wrote:
>
>>
>> I removed the separate pg_file_length() function, as it doesn't have any
>> significant notational advantage anymore; you can do
>
>
> Please note that there are pg_file_length functions in use for 8.0 on
> probably >95 % of win32 installations, so you're breaking backwards
> compatibility.
>
>

If the windows packagers have added extra functions into their build of
postgres, then they can maintain them, no? Of course, this would
illustrate the danger of such a practice. Postgres is surely only
obligated to try not to break backwards compatibility with its own
released code.

cheers

andrew

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-08-14 16:56:06 Re: PATCH to allow concurrent VACUUMs to not lock each
Previous Message Martijn van Oosterhout 2005-08-14 12:24:19 Re: [PATCH] Clarify issues with SPI and C language function limitations