From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file |
Date: | 2015-07-17 03:17:52 |
Message-ID: | CA+TgmoZrg9hFuq4cHEcOFSK39Rmp_nCagPWqwPJPA3q2G2hmsw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Thu, Jul 16, 2015 at 9:54 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> Isn't this "rule" confusing the administrators?
I'd like to think not, but yeah, it probably is. It is not like it
isn't documented. There are even comments in postgresql.conf
explaining it. But the fact that we have committers who are confused
probably isn't a great sign.
I really rather like the system we have and find it quite intuitive,
but it's obvious that a lot of other people don't.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2015-07-17 03:22:54 | Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file |
Previous Message | Tom Lane | 2015-07-17 02:58:26 | pgsql: Fix a low-probability crash in our qsort implementation. |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-07-17 03:18:34 | Re: proposal: multiple psql option -c |
Previous Message | Tom Lane | 2015-07-17 03:05:21 | Re: RFC: replace pg_stat_activity.waiting with something more descriptive |