From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Asbjørn Sloth Tønnesen <asbjorn(at)asbjorn(dot)it>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH 0/3] Tau support |
Date: | 2014-06-28 02:27:54 |
Message-ID: | CA+TgmoawbmyZ6kQBg2XfrmF=y1NFTZ10fGwEVpX2QhP05_AVrQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 27, 2014 at 9:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> =?UTF-8?q?Asbj=C3=B8rn=20Sloth=20T=C3=B8nnesen?= <asbjorn(at)asbjorn(dot)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:
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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-06-28 02:34:19 | Re: Spinlocks and compiler/memory barriers |
Previous Message | David Fetter | 2014-06-28 01:59:41 | Re: [PATCH 0/3] Tau support |