Re: [PATCH 0/3] Tau support - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH 0/3] Tau support
Date
Msg-id CA+TgmoawbmyZ6kQBg2XfrmF=y1NFTZ10fGwEVpX2QhP05_AVrQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH 0/3] Tau support  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jun 27, 2014 at 9:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Asbjørn Sloth Tønnesen <asbjorn@asbjorn.it> writes:
>> Please see the following patches for implementing support
>> for and migrating to Tau in PostgreSQL.
>
> While I don't particularly object to adding a tau() function, the rest of
> this seems like change for the sake of change.  What's the point?  And
> it had better be a darn good point, because cross-version code differences
> are a constant source of maintenance pain for us.  We don't need ones
> that have no concrete value.

Perhaps we should also have a pau() function, as proposed here:

http://xkcd.com/1292/

On a related note, I think we should declare "vi" the officially
favored editor of the PostgreSQL project.

(Note: No, I'm not serious.)

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



pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: [PATCH 0/3] Tau support
Next
From: Robert Haas
Date:
Subject: Re: Spinlocks and compiler/memory barriers