| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Antonio Belloni <abelloni(at)rioservice(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Contributing with code |
| Date: | 2017-12-31 18:35:08 |
| Message-ID: | CA+TgmoZC3CyzZDY1fWChRNOY-5SBjUkB1w=C6y6JmQHtAVukjw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 28, 2017 at 5:42 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> Well, it's arguably solveable, if the solution is to allow at least limited
> cross-database access to catalog relations.
I think this is a bad idea. It's bound to add complexity and
fragility to the system and I don't think it's worth it.
Also, let's delete the TODO list. People keep using it as a source of
project ideas, and that's bad.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Flower | 2017-12-31 18:41:03 | Re: What does Time.MAX_VALUE actually represent? |
| Previous Message | Robert Haas | 2017-12-31 18:27:50 | Re: Re: PATCH: Configurable file mode mask |